Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db924e85b54e859098ff6d0ec45efa4a2ecc3dda23be6f080953c5257b86f5d0

Tx prefix hash: 900e334b6ace9903e0c438f670d354b7f2618d9f4039048870115a7cab5be124
Tx public key: cde0e8c1f73f6ab157c3701375d280a33b5aac2be5103e420df735b99d3eeebc
Timestamp: 1581085250 Timestamp [UCT]: 2020-02-07 14:20:50 Age [y:d:h:m:s]: 05:040:19:37:00
Block: 60290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181616 RingCT/type: yes/0
Extra: 01cde0e8c1f73f6ab157c3701375d280a33b5aac2be5103e420df735b99d3eeebc02110000000212c4732d000000000000000000

1 output(s) for total of 387.473957784000 dcy

stealth address amount amount idx
00: f9aeb08499aa8d00744ec0c5087ef81b1561334ecfc4e750b3c2cc160a3851e8 387.473957784000 111176 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": 60300, "vin": [ { "gen": { "height": 60290 } } ], "vout": [ { "amount": 387473957784, "target": { "key": "f9aeb08499aa8d00744ec0c5087ef81b1561334ecfc4e750b3c2cc160a3851e8" } } ], "extra": [ 1, 205, 224, 232, 193, 247, 63, 106, 177, 87, 195, 112, 19, 117, 210, 128, 163, 59, 90, 172, 43, 229, 16, 62, 66, 13, 247, 53, 185, 157, 62, 238, 188, 2, 17, 0, 0, 0, 2, 18, 196, 115, 45, 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