Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5238b08a725001090de02e82a52b746ba87743dc3f57ef934b360e2b94b0c06

Tx prefix hash: 3767b841f48d9d15f1f57f219cecf798b97bfc8bbf7d114cec4d266e5d9be684
Tx public key: 7cd8ddb3d0ec4a629863d5fde8d3ed30e57dc826cce7b832a6f449b37e1ea2d8
Timestamp: 1700124473 Timestamp [UCT]: 2023-11-16 08:47:53 Age [y:d:h:m:s]: 01:153:20:22:46
Block: 892778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371141 RingCT/type: yes/0
Extra: 017cd8ddb3d0ec4a629863d5fde8d3ed30e57dc826cce7b832a6f449b37e1ea2d8021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.675858640000 dcy

stealth address amount amount idx
00: 04d3d090515ab0d4115e6021bd380ecc42a7f000df05d7cad7f146a62b2980ad 0.675858640000 1348909 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": 892788, "vin": [ { "gen": { "height": 892778 } } ], "vout": [ { "amount": 675858640, "target": { "key": "04d3d090515ab0d4115e6021bd380ecc42a7f000df05d7cad7f146a62b2980ad" } } ], "extra": [ 1, 124, 216, 221, 179, 208, 236, 74, 98, 152, 99, 213, 253, 232, 211, 237, 48, 229, 125, 200, 38, 204, 231, 184, 50, 166, 244, 73, 179, 126, 30, 162, 216, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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