Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45ba646721f420ddbb226258b1f51c4175af8290372d3ef62439dfec58b6f80e

Tx prefix hash: 3042d3fbcc401b9f0b309051660ad9d6253fe73a5026d5e6315069098cb2c529
Tx public key: 1e475213cab7d0b36cfdc76722fa458cbef07e23aa26d61c619741a921e7e3fa
Timestamp: 1703608029 Timestamp [UCT]: 2023-12-26 16:27:09 Age [y:d:h:m:s]: 01:341:14:46:41
Block: 921659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503015 RingCT/type: yes/0
Extra: 011e475213cab7d0b36cfdc76722fa458cbef07e23aa26d61c619741a921e7e3fa02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eed74335ebf31ba974cb14efc72627ec68fe2e8975ed3c249d7de9f66e052ec8 0.600000000000 1379349 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": 921669, "vin": [ { "gen": { "height": 921659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eed74335ebf31ba974cb14efc72627ec68fe2e8975ed3c249d7de9f66e052ec8" } } ], "extra": [ 1, 30, 71, 82, 19, 202, 183, 208, 179, 108, 253, 199, 103, 34, 250, 69, 140, 190, 240, 126, 35, 170, 38, 214, 28, 97, 151, 65, 169, 33, 231, 227, 250, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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