Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3003fdceda2d04dd8f9f9d761ee44f44e86f0a9a18c6c23798694055572ff1bc

Tx prefix hash: a29b009489f4558edf1ac0a4f5c87eb6a1c65d69dad031e41c5495bfd1522936
Tx public key: ec22a5e8808ea28cda6d936cc0676c38b00939739768316dddc73ea79c58ebfb
Timestamp: 1709245308 Timestamp [UCT]: 2024-02-29 22:21:48 Age [y:d:h:m:s]: 01:264:23:30:24
Block: 968401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448114 RingCT/type: yes/0
Extra: 01ec22a5e8808ea28cda6d936cc0676c38b00939739768316dddc73ea79c58ebfb0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b8bd343d99e81c479d9ea2848fc92cdc22e8395a0a7b441de08bae4c52cf926 0.600000000000 1428216 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": 968411, "vin": [ { "gen": { "height": 968401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b8bd343d99e81c479d9ea2848fc92cdc22e8395a0a7b441de08bae4c52cf926" } } ], "extra": [ 1, 236, 34, 165, 232, 128, 142, 162, 140, 218, 109, 147, 108, 192, 103, 108, 56, 176, 9, 57, 115, 151, 104, 49, 109, 221, 199, 62, 167, 156, 88, 235, 251, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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