Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7234dd5e74b6d02d17a7a992d5aaf3deb341022ec39869b4cccb3b83f63503ca

Tx prefix hash: 5360c681c532f5acda11770084ab45f8349aa08d9f6985e7d3e1fad999cac119
Tx public key: a090299c47550fa9c04c4a0bc7ff5d8a12e9b51f88246b7da0b489aad28cdd6c
Timestamp: 1766242618 Timestamp [UCT]: 2025-12-20 14:56:58 Age [y:d:h:m:s]: 00:002:08:47:30
Block: 1437797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1688 RingCT/type: yes/0
Extra: 01a090299c47550fa9c04c4a0bc7ff5d8a12e9b51f88246b7da0b489aad28cdd6c0211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10e5b95eca370cdad69c4a911b9d6e45957a8a2512d0b444f123662395278eea 0.600000000000 1926608 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": 1437807, "vin": [ { "gen": { "height": 1437797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10e5b95eca370cdad69c4a911b9d6e45957a8a2512d0b444f123662395278eea" } } ], "extra": [ 1, 160, 144, 41, 156, 71, 85, 15, 169, 192, 76, 74, 11, 199, 255, 93, 138, 18, 233, 181, 31, 136, 36, 107, 125, 160, 180, 137, 170, 210, 140, 221, 108, 2, 17, 0, 0, 0, 1, 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