Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ee94107c193f30c3fcb3c4342eab2180f1246794a4c45a94b155c993d1d7b63

Tx prefix hash: 514c378105792a777471e79f0f0744a74656391de464431fc98e9cf2d0b18252
Tx public key: be4b8df76a6d4bd1c0168836d5290cca97c28538c314d9aa751a17489139162b
Timestamp: 1704552941 Timestamp [UCT]: 2024-01-06 14:55:41 Age [y:d:h:m:s]: 01:051:14:13:11
Block: 929476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297955 RingCT/type: yes/0
Extra: 01be4b8df76a6d4bd1c0168836d5290cca97c28538c314d9aa751a17489139162b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f6a0e78f5959f5fab43f73e326f966e938e156eaa9e501ce488933aa792d62d 0.600000000000 1387352 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": 929486, "vin": [ { "gen": { "height": 929476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f6a0e78f5959f5fab43f73e326f966e938e156eaa9e501ce488933aa792d62d" } } ], "extra": [ 1, 190, 75, 141, 247, 106, 109, 75, 209, 192, 22, 136, 54, 213, 41, 12, 202, 151, 194, 133, 56, 195, 20, 217, 170, 117, 26, 23, 72, 145, 57, 22, 43, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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