Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c3e427622f183d5d0ded8949bb2caca0fba5919a231768b90717bd68b9533b5

Tx prefix hash: a160fa05307776b715b15eb96e54f55c2de3ec669d5b3db0eea6f618c6bffba3
Tx public key: 0cad2627c3ecd2ab820e787542381f4c01099e4e126dece43593b18fafd0c2b5
Timestamp: 1764115664 Timestamp [UCT]: 2025-11-26 00:07:44 Age [y:d:h:m:s]: 00:027:03:34:30
Block: 1420170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19434 RingCT/type: yes/0
Extra: 010cad2627c3ecd2ab820e787542381f4c01099e4e126dece43593b18fafd0c2b50211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cd11ad9207b385d03bdc8314d210806f711c717f7e3cdcbca19b49dbc3f1da4 0.600000000000 1908711 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": 1420180, "vin": [ { "gen": { "height": 1420170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cd11ad9207b385d03bdc8314d210806f711c717f7e3cdcbca19b49dbc3f1da4" } } ], "extra": [ 1, 12, 173, 38, 39, 195, 236, 210, 171, 130, 14, 120, 117, 66, 56, 31, 76, 1, 9, 158, 78, 18, 109, 236, 228, 53, 147, 177, 143, 175, 208, 194, 181, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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