Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70ea0c0ffa8bd4194f9dab67104d8823bb58bf48bc4ed3aa12ddbbb42d30f227

Tx prefix hash: bb023ee7621de9b4d825c5766e652364f33726e334f58e5e5c39c8a328e98e10
Tx public key: c96cad67cf6de936ba1a1bfe6bb6c1533b5e37409921dad46695d5dc418a77a7
Timestamp: 1700245250 Timestamp [UCT]: 2023-11-17 18:20:50 Age [y:d:h:m:s]: 01:143:22:19:55
Block: 893785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364039 RingCT/type: yes/0
Extra: 01c96cad67cf6de936ba1a1bfe6bb6c1533b5e37409921dad46695d5dc418a77a702110000001033af99f4000000000000000000

1 output(s) for total of 0.670686029000 dcy

stealth address amount amount idx
00: 0354b5be47210d14188b79be7408216aca33b6e09231f3400628b4a2d41dca06 0.670686029000 1349970 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": 893795, "vin": [ { "gen": { "height": 893785 } } ], "vout": [ { "amount": 670686029, "target": { "key": "0354b5be47210d14188b79be7408216aca33b6e09231f3400628b4a2d41dca06" } } ], "extra": [ 1, 201, 108, 173, 103, 207, 109, 233, 54, 186, 26, 27, 254, 107, 182, 193, 83, 59, 94, 55, 64, 153, 33, 218, 212, 102, 149, 213, 220, 65, 138, 119, 167, 2, 17, 0, 0, 0, 16, 51, 175, 153, 244, 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