Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7741c5042e5be9de54867b94d2623caa19902b581a6000e46a4a96846deaeee

Tx prefix hash: 6f3bb021ed57b97b1dd5be70892c678f0e0263bcbf6ac9794789232e552cde82
Tx public key: efe80e8085d3d7faf755fc4382aa8b0e7ad3e362441482f6a5735d3d4a2c524d
Timestamp: 1751290440 Timestamp [UCT]: 2025-06-30 13:34:00 Age [y:d:h:m:s]: 00:181:18:11:57
Block: 1315870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128151 RingCT/type: yes/0
Extra: 01efe80e8085d3d7faf755fc4382aa8b0e7ad3e362441482f6a5735d3d4a2c524d02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97a2044e565592aeb7595076f9ba830ea53e13b7f5c640e16c0412e1668513fe 0.600000000000 1803527 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": 1315880, "vin": [ { "gen": { "height": 1315870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97a2044e565592aeb7595076f9ba830ea53e13b7f5c640e16c0412e1668513fe" } } ], "extra": [ 1, 239, 232, 14, 128, 133, 211, 215, 250, 247, 85, 252, 67, 130, 170, 139, 14, 122, 211, 227, 98, 68, 20, 130, 246, 165, 115, 93, 61, 74, 44, 82, 77, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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