Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82905dcfe086e7a6c24ac8c28b57414528875f22191fb493f5483f1804050f04

Tx prefix hash: 59609a3ca1e1b1e354eb15f4b3da79bf0e76c2c65f8f057890a77d48a52fb943
Tx public key: 15391a15d11abf54511a8b794c3740510a04334d04a5ed1dbabd3fdef2ecdb05
Timestamp: 1699527462 Timestamp [UCT]: 2023-11-09 10:57:42 Age [y:d:h:m:s]: 01:131:12:38:18
Block: 887838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355199 RingCT/type: yes/0
Extra: 0115391a15d11abf54511a8b794c3740510a04334d04a5ed1dbabd3fdef2ecdb050211000000044b8f5122000000000000000000

1 output(s) for total of 0.701817427000 dcy

stealth address amount amount idx
00: 8a106c9d57e454021b7cf5368c404294084bf7db6656194ca7cdc780214c3aff 0.701817427000 1343743 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": 887848, "vin": [ { "gen": { "height": 887838 } } ], "vout": [ { "amount": 701817427, "target": { "key": "8a106c9d57e454021b7cf5368c404294084bf7db6656194ca7cdc780214c3aff" } } ], "extra": [ 1, 21, 57, 26, 21, 209, 26, 191, 84, 81, 26, 139, 121, 76, 55, 64, 81, 10, 4, 51, 77, 4, 165, 237, 29, 186, 189, 63, 222, 242, 236, 219, 5, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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