Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 128efd61798d745f23343741c15f505b5291c4f487aa34d5677a087b332aaff0

Tx prefix hash: 3c5884626b2c66f4c51efd499d53c8842e3357d50ee995bd2b45541e0abddb24
Tx public key: 511d35baf789a086190f969611a7e94c9069e84f4a24c1775d66e28515e7ca3c
Timestamp: 1675106700 Timestamp [UCT]: 2023-01-30 19:25:00 Age [y:d:h:m:s]: 01:294:10:05:03
Block: 686238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471371 RingCT/type: yes/0
Extra: 01511d35baf789a086190f969611a7e94c9069e84f4a24c1775d66e28515e7ca3c02110000000b5029cbac000000000000000000

1 output(s) for total of 3.267447126000 dcy

stealth address amount amount idx
00: 4002906d4c542acdf5f68b3415a81a942466ec60191c0fbf19d2c9dfc8e65dc2 3.267447126000 1128717 of 0

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": 686248, "vin": [ { "gen": { "height": 686238 } } ], "vout": [ { "amount": 3267447126, "target": { "key": "4002906d4c542acdf5f68b3415a81a942466ec60191c0fbf19d2c9dfc8e65dc2" } } ], "extra": [ 1, 81, 29, 53, 186, 247, 137, 160, 134, 25, 15, 150, 150, 17, 167, 233, 76, 144, 105, 232, 79, 74, 36, 193, 119, 93, 102, 226, 133, 21, 231, 202, 60, 2, 17, 0, 0, 0, 11, 80, 41, 203, 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