Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1620a8c8add6a0bca8a8665ac8533c623f0b47643b3d87fe4869f30ead27929c

Tx prefix hash: ee78b60f31a008a8175f09cc538f19ef7b6ca2698db845a8c91062cb1d18cc19
Tx public key: 4292413e9e05273e04dd1dd3ca15eb7cfc98240eb351dc962fd4c3d3b7fe6d04
Timestamp: 1698039105 Timestamp [UCT]: 2023-10-23 05:31:45 Age [y:d:h:m:s]: 01:123:06:12:02
Block: 875697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349054 RingCT/type: yes/0
Extra: 014292413e9e05273e04dd1dd3ca15eb7cfc98240eb351dc962fd4c3d3b7fe6d0402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.769931944000 dcy

stealth address amount amount idx
00: fc971ce1b2dd5cab7aa09b0839b04ae9096312feeafc67efb8128f41a544ff23 0.769931944000 1330961 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": 875707, "vin": [ { "gen": { "height": 875697 } } ], "vout": [ { "amount": 769931944, "target": { "key": "fc971ce1b2dd5cab7aa09b0839b04ae9096312feeafc67efb8128f41a544ff23" } } ], "extra": [ 1, 66, 146, 65, 62, 158, 5, 39, 62, 4, 221, 29, 211, 202, 21, 235, 124, 252, 152, 36, 14, 179, 81, 220, 150, 47, 212, 195, 211, 183, 254, 109, 4, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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