Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c05b7ef5773e0a7d807aeaf15ec60eb76b48ccd3a4334c9389be78b14d21d1b6

Tx prefix hash: 3172e7c001bf62426203c4f1d2828bc717ff59fc9d59f3d26e7207e4b3775780
Tx public key: 99e93c811c49ecca3537d0b888b73b6111cd38960d36c2d7c1c3125917a42a4e
Timestamp: 1766148715 Timestamp [UCT]: 2025-12-19 12:51:55 Age [y:d:h:m:s]: 00:004:05:05:49
Block: 1437009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3018 RingCT/type: yes/0
Extra: 0199e93c811c49ecca3537d0b888b73b6111cd38960d36c2d7c1c3125917a42a4e0211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44c25c153c431eafe796401e5a4365c80b34f93759a1dbe8f491095c5bd05de8 0.600000000000 1925814 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": 1437019, "vin": [ { "gen": { "height": 1437009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44c25c153c431eafe796401e5a4365c80b34f93759a1dbe8f491095c5bd05de8" } } ], "extra": [ 1, 153, 233, 60, 129, 28, 73, 236, 202, 53, 55, 208, 184, 136, 183, 59, 97, 17, 205, 56, 150, 13, 54, 194, 215, 193, 195, 18, 89, 23, 164, 42, 78, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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