Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74e2879769cc8c291cd150c819586330670dd14267ee8edffea4d8a3dfd4decc

Tx prefix hash: 6f30aed0673cec87af797125ed99f7402d8984dd55e1f2ab2e0564fb667070a5
Tx public key: 6d305d808ed15a1f20963a8c5e3bd5dcf4b9837415a24e9e7fb2c0e4cb777df3
Timestamp: 1763311559 Timestamp [UCT]: 2025-11-16 16:45:59 Age [y:d:h:m:s]: 00:004:21:22:08
Block: 1413497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3498 RingCT/type: yes/0
Extra: 016d305d808ed15a1f20963a8c5e3bd5dcf4b9837415a24e9e7fb2c0e4cb777df302110000000317b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a1401a7dcbf5b973d770fbf380f7110f8c62644286256c16a370f2af7195309 0.600000000000 1901976 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": 1413507, "vin": [ { "gen": { "height": 1413497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a1401a7dcbf5b973d770fbf380f7110f8c62644286256c16a370f2af7195309" } } ], "extra": [ 1, 109, 48, 93, 128, 142, 209, 90, 31, 32, 150, 58, 140, 94, 59, 213, 220, 244, 185, 131, 116, 21, 162, 78, 158, 127, 178, 192, 228, 203, 119, 125, 243, 2, 17, 0, 0, 0, 3, 23, 177, 145, 50, 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