Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c070848dfd00bddfb498afb2c3f2e1e94dfdb639398946f24b8df4e447103d79

Tx prefix hash: 7013a1f596b9fb5ab467b634c26d7a3767d34e10e0fc1b0b8bd06e882235f1ed
Tx public key: 9914493bacfcd13b24a711c0586e9bfd0790e62767c38d62fe5118672fb7b343
Timestamp: 1765472617 Timestamp [UCT]: 2025-12-11 17:03:37 Age [y:d:h:m:s]: 00:029:20:41:24
Block: 1431414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21383 RingCT/type: yes/0
Extra: 019914493bacfcd13b24a711c0586e9bfd0790e62767c38d62fe5118672fb7b343021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc29e0e693b4121adeb353997f034dbcaaac2ebab205f78e6a2e13e4a6c51aab 0.600000000000 1920183 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1431424, "vin": [ { "gen": { "height": 1431414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc29e0e693b4121adeb353997f034dbcaaac2ebab205f78e6a2e13e4a6c51aab" } } ], "extra": [ 1, 153, 20, 73, 59, 172, 252, 209, 59, 36, 167, 17, 192, 88, 110, 155, 253, 7, 144, 230, 39, 103, 195, 141, 98, 254, 81, 24, 103, 47, 183, 179, 67, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8