Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec99b97aa0c35edd849e7d35902651a9716f31eddb9f3018e888b184507146cd

Tx prefix hash: b7ce80b63c05f05ff1e59f83443bc100e5c1e172961d7556a22f12d59ec9d2b1
Tx public key: 496c70f3c341576afdac4585b6fe98edc91cde6f3265be0f264e1ca3e341dbb5
Timestamp: 1673384123 Timestamp [UCT]: 2023-01-10 20:55:23 Age [y:d:h:m:s]: 02:107:20:09:08
Block: 671943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 598772 RingCT/type: yes/0
Extra: 01496c70f3c341576afdac4585b6fe98edc91cde6f3265be0f264e1ca3e341dbb502110000000174b6d784000000000000000000

1 output(s) for total of 3.643962161000 dcy

stealth address amount amount idx
00: bcb1fb2945bf41c69e1c15ca410c185e8ddac25948c34631133a37d75a575712 3.643962161000 1113454 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": 671953, "vin": [ { "gen": { "height": 671943 } } ], "vout": [ { "amount": 3643962161, "target": { "key": "bcb1fb2945bf41c69e1c15ca410c185e8ddac25948c34631133a37d75a575712" } } ], "extra": [ 1, 73, 108, 112, 243, 195, 65, 87, 106, 253, 172, 69, 133, 182, 254, 152, 237, 201, 28, 222, 111, 50, 101, 190, 15, 38, 78, 28, 163, 227, 65, 219, 181, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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