Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2aec7179931881730b6900ee5f615aacf09b04bc991a83bbb5148d5493b9fdd9

Tx prefix hash: 57e226eee1a5857d59c66873d151d8e4e400fbaa6546eaec75e66547047fce77
Tx public key: f97825c3dd829e42471679962f38e6a3c21c3bbc79efb8dc3b83ea46438afb7b
Timestamp: 1756099407 Timestamp [UCT]: 2025-08-25 05:23:27 Age [y:d:h:m:s]: 00:088:19:03:14
Block: 1353910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63397 RingCT/type: yes/0
Extra: 01f97825c3dd829e42471679962f38e6a3c21c3bbc79efb8dc3b83ea46438afb7b0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01ccdb4593521514d7d8093d392af49606bd0e9aab0e5534858087a29f847f7c 0.600000000000 1841889 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": 1353920, "vin": [ { "gen": { "height": 1353910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01ccdb4593521514d7d8093d392af49606bd0e9aab0e5534858087a29f847f7c" } } ], "extra": [ 1, 249, 120, 37, 195, 221, 130, 158, 66, 71, 22, 121, 150, 47, 56, 230, 163, 194, 28, 59, 188, 121, 239, 184, 220, 59, 131, 234, 70, 67, 138, 251, 123, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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