Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52f0c53ed454c6c262c00d31dc4bebdd757af3e2856215cf83a149ffc555835c

Tx prefix hash: 522ef346ffd3e7028ea08b9347cadb6754eb961544761b9e09809d74253545bd
Tx public key: 4bfbba0b6d7b5285c9ef6ab19d429c960b8e39c5a9846a5fa09d76b709987baf
Timestamp: 1752026180 Timestamp [UCT]: 2025-07-09 01:56:20 Age [y:d:h:m:s]: 00:166:14:45:23
Block: 1321664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117613 RingCT/type: yes/0
Extra: 014bfbba0b6d7b5285c9ef6ab19d429c960b8e39c5a9846a5fa09d76b709987baf0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e45578e4460e5ca9dea91a508a43e3a8b077225d0ab3c1339d9d8d1dc22eb477 0.600000000000 1809371 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": 1321674, "vin": [ { "gen": { "height": 1321664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e45578e4460e5ca9dea91a508a43e3a8b077225d0ab3c1339d9d8d1dc22eb477" } } ], "extra": [ 1, 75, 251, 186, 11, 109, 123, 82, 133, 201, 239, 106, 177, 157, 66, 156, 150, 11, 142, 57, 197, 169, 132, 106, 95, 160, 157, 118, 183, 9, 152, 123, 175, 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