Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7502e3c98e32d324b8f702f69b6fc7e312d9e0e8747d07ee7f98486d285fdbd

Tx prefix hash: f3e3d753ea0dcd2a4ed79a0380b5c3230ff9a64057e4ef8d9aad9889b721a3b1
Tx public key: 569b83d4168dadee28f8d441487c2a87d2b2f8916a781177e7919d6399e67ed1
Timestamp: 1612734423 Timestamp [UCT]: 2021-02-07 21:47:03 Age [y:d:h:m:s]: 03:271:23:30:49
Block: 194089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 953247 RingCT/type: yes/0
Extra: 01569b83d4168dadee28f8d441487c2a87d2b2f8916a781177e7919d6399e67ed1021100000019aad74b3a000000000000000000

1 output(s) for total of 139.605717290000 dcy

stealth address amount amount idx
00: ffc3c23816e5bbeadf8a3093161c71b00206a5d15403b25c241e1cdfb8dfb1db 139.605717290000 393543 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": 194099, "vin": [ { "gen": { "height": 194089 } } ], "vout": [ { "amount": 139605717290, "target": { "key": "ffc3c23816e5bbeadf8a3093161c71b00206a5d15403b25c241e1cdfb8dfb1db" } } ], "extra": [ 1, 86, 155, 131, 212, 22, 141, 173, 238, 40, 248, 212, 65, 72, 124, 42, 135, 210, 178, 248, 145, 106, 120, 17, 119, 231, 145, 157, 99, 153, 230, 126, 209, 2, 17, 0, 0, 0, 25, 170, 215, 75, 58, 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