Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd2f84fa7dca9d886e51feae8fecd6614b9dcde69db2ebea1dad7bf54eee642f

Tx prefix hash: f326ef50dc29662b23a92ae856737027f8342fd20aad20f0bd80c0f83924325e
Tx public key: 462ed9ab29e02bb8fb57eb9c392775bbe6333b8f268c4916fd6c0cc93d0c9cc3
Timestamp: 1704381536 Timestamp [UCT]: 2024-01-04 15:18:56 Age [y:d:h:m:s]: 01:126:23:26:24
Block: 928077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351862 RingCT/type: yes/0
Extra: 01462ed9ab29e02bb8fb57eb9c392775bbe6333b8f268c4916fd6c0cc93d0c9cc302110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9667b268169b999214768d9161f8f33dc06ea44f9a4f1668107ff338fe24e275 0.600000000000 1385933 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": 928087, "vin": [ { "gen": { "height": 928077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9667b268169b999214768d9161f8f33dc06ea44f9a4f1668107ff338fe24e275" } } ], "extra": [ 1, 70, 46, 217, 171, 41, 224, 43, 184, 251, 87, 235, 156, 57, 39, 117, 187, 230, 51, 59, 143, 38, 140, 73, 22, 253, 108, 12, 201, 61, 12, 156, 195, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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