Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c9b50a5dc8fa2e58262a703867f3ca5b886d6b55b660116c55fe763f8800aad

Tx prefix hash: d534fee941dcc126b2fe56ecb862492413462fbc486688cbc97457246c4422a9
Tx public key: 78ffc66dc4fcf5269ae41343fe79ef2e20bbc111cc04fbe9bdb4738a5e79f37b
Timestamp: 1765321218 Timestamp [UCT]: 2025-12-09 23:00:18 Age [y:d:h:m:s]: 00:012:15:12:18
Block: 1430153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9054 RingCT/type: yes/0
Extra: 0178ffc66dc4fcf5269ae41343fe79ef2e20bbc111cc04fbe9bdb4738a5e79f37b02110000000670609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f64b73231f5ae2c50bf8511f5732cd5c660942b56dfdbb936b653d526e69e9e1 0.600000000000 1918896 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": 1430163, "vin": [ { "gen": { "height": 1430153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f64b73231f5ae2c50bf8511f5732cd5c660942b56dfdbb936b653d526e69e9e1" } } ], "extra": [ 1, 120, 255, 198, 109, 196, 252, 245, 38, 154, 228, 19, 67, 254, 121, 239, 46, 32, 187, 193, 17, 204, 4, 251, 233, 189, 180, 115, 138, 94, 121, 243, 123, 2, 17, 0, 0, 0, 6, 112, 96, 157, 3, 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