Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3021b68521ca94e39780ef0f9d62b582d706b1ae465f2dc6b007562cea0939cb

Tx prefix hash: 52db06d5af23d909a18c2c2f2821ef2b25cfb0c8056a992c40d511edec996676
Tx public key: ba7c1e825345c64c2f7f584b797fac909d0cb7718596422fd2f8599d51b852e6
Timestamp: 1754114766 Timestamp [UCT]: 2025-08-02 06:06:06 Age [y:d:h:m:s]: 00:109:08:02:27
Block: 1338542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77029 RingCT/type: yes/0
Extra: 01ba7c1e825345c64c2f7f584b797fac909d0cb7718596422fd2f8599d51b852e6021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c01ce1782bf5181435c0d3eb78b44f85bba5bf5686d33497242077741ebf69b 0.600000000000 1826351 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": 1338552, "vin": [ { "gen": { "height": 1338542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c01ce1782bf5181435c0d3eb78b44f85bba5bf5686d33497242077741ebf69b" } } ], "extra": [ 1, 186, 124, 30, 130, 83, 69, 198, 76, 47, 127, 88, 75, 121, 127, 172, 144, 157, 12, 183, 113, 133, 150, 66, 47, 210, 248, 89, 157, 81, 184, 82, 230, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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