Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee5b4e2aec0a49cb4c552a08d783faf7c034f575216e37e4fc7bedf0794d245a

Tx prefix hash: 97748f4498d65372beca788c329b206010146a40799eb48755f705da6c2ffe05
Tx public key: 0cdb80bd6e256957a0c213f91dff72d9a0a7061748bb1554a8ab6704de840967
Timestamp: 1731920400 Timestamp [UCT]: 2024-11-18 09:00:00 Age [y:d:h:m:s]: 00:212:23:28:22
Block: 1156283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151953 RingCT/type: yes/0
Extra: 010cdb80bd6e256957a0c213f91dff72d9a0a7061748bb1554a8ab6704de840967021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4acfbc1e81376dc8699a207d9c50bdc1a03a184ced1f9c5489a3be951a8e6ad7 0.600000000000 1641906 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": 1156293, "vin": [ { "gen": { "height": 1156283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4acfbc1e81376dc8699a207d9c50bdc1a03a184ced1f9c5489a3be951a8e6ad7" } } ], "extra": [ 1, 12, 219, 128, 189, 110, 37, 105, 87, 160, 194, 19, 249, 29, 255, 114, 217, 160, 167, 6, 23, 72, 187, 21, 84, 168, 171, 103, 4, 222, 132, 9, 103, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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