Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ac1dff2257031d0638de9ea220371fe81e9d76e48017b1eb0580789ccc515b2

Tx prefix hash: 4b0210b9f0c6c6aa9835def460464e334476ce56c1b50c13557dc17014dbf6be
Tx public key: 48903a33e0b9e6d460f1a441fbfbc52d17d600572e45c9093676b3690ea257d9
Timestamp: 1749750507 Timestamp [UCT]: 2025-06-12 17:48:27 Age [y:d:h:m:s]: 00:152:17:22:19
Block: 1303605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106868 RingCT/type: yes/0
Extra: 0148903a33e0b9e6d460f1a441fbfbc52d17d600572e45c9093676b3690ea257d9021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a885755c2d3d63601118dcafdaa5e5e3f373e4fd6ae4c08d7ee33ace549d85ae 0.600000000000 1791188 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": 1303615, "vin": [ { "gen": { "height": 1303605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a885755c2d3d63601118dcafdaa5e5e3f373e4fd6ae4c08d7ee33ace549d85ae" } } ], "extra": [ 1, 72, 144, 58, 51, 224, 185, 230, 212, 96, 241, 164, 65, 251, 251, 197, 45, 23, 214, 0, 87, 46, 69, 201, 9, 54, 118, 179, 105, 14, 162, 87, 217, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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