Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83990c507af2fbf6bfa53bd1cb2c8633329b0c8cff815e3f3906ccda8c826d92

Tx prefix hash: f7f6282359cd9027e8f1a7291fc40d5925365a5e33824fea0d19a52a9bca9407
Tx public key: 59e2f3012b2734f33effe04e84a3d7a143a76e8bd7bb374fc3b3847adff40c44
Timestamp: 1722404843 Timestamp [UCT]: 2024-07-31 05:47:23 Age [y:d:h:m:s]: 00:116:17:37:47
Block: 1077491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83524 RingCT/type: yes/0
Extra: 0159e2f3012b2734f33effe04e84a3d7a143a76e8bd7bb374fc3b3847adff40c44021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95ca0070ced4c64ea63539a6a05cdd9aa29fb25d707d8754b6e3219b2bc1f155 0.600000000000 1550040 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": 1077501, "vin": [ { "gen": { "height": 1077491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95ca0070ced4c64ea63539a6a05cdd9aa29fb25d707d8754b6e3219b2bc1f155" } } ], "extra": [ 1, 89, 226, 243, 1, 43, 39, 52, 243, 62, 255, 224, 78, 132, 163, 215, 161, 67, 167, 110, 139, 215, 187, 55, 79, 195, 179, 132, 122, 223, 244, 12, 68, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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