Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eff5a5b377a3959afdc077e0aa531d6e2057c277d7a398289fc2098158d8df59

Tx prefix hash: f2914e70e70e99771cf3688258e94bd62b2d0e5222ae7a59dbaa6ed3f1d3038c
Tx public key: ff74b781f9a31cb4e58459a8f86fee44ad9fdc52fd146586ae895e28ddfc17a7
Timestamp: 1700022899 Timestamp [UCT]: 2023-11-15 04:34:59 Age [y:d:h:m:s]: 01:126:02:15:34
Block: 891938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351307 RingCT/type: yes/0
Extra: 01ff74b781f9a31cb4e58459a8f86fee44ad9fdc52fd146586ae895e28ddfc17a702110000000575e3f0e9000000000000000000

1 output(s) for total of 0.680203935000 dcy

stealth address amount amount idx
00: e9df35d9bbc0aa3674fc32781792b84ef94f6af1271c528ed9d7ff3fa4b84087 0.680203935000 1347993 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": 891948, "vin": [ { "gen": { "height": 891938 } } ], "vout": [ { "amount": 680203935, "target": { "key": "e9df35d9bbc0aa3674fc32781792b84ef94f6af1271c528ed9d7ff3fa4b84087" } } ], "extra": [ 1, 255, 116, 183, 129, 249, 163, 28, 180, 229, 132, 89, 168, 248, 111, 238, 68, 173, 159, 220, 82, 253, 20, 101, 134, 174, 137, 94, 40, 221, 252, 23, 167, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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