Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5379ae65a071d7f2a68a5b630d81287e616fe27886666855e0d9e4dcdb2e5e8b

Tx prefix hash: fd296bb41eb069d245074cc3ff179a04a79c1f1f5df623fa253b91879b613715
Tx public key: eb9b22769e398d981be35802231f3e29ec836f4666e5a32ae6ee8bef680e2364
Timestamp: 1720995563 Timestamp [UCT]: 2024-07-14 22:19:23 Age [y:d:h:m:s]: 00:265:08:15:27
Block: 1065820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189559 RingCT/type: yes/0
Extra: 01eb9b22769e398d981be35802231f3e29ec836f4666e5a32ae6ee8bef680e236402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6e4e8fa7c085329ea79222147956dfe2a639433292cc97bce29eb3c8d247c36 0.600000000000 1536375 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": 1065830, "vin": [ { "gen": { "height": 1065820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6e4e8fa7c085329ea79222147956dfe2a639433292cc97bce29eb3c8d247c36" } } ], "extra": [ 1, 235, 155, 34, 118, 158, 57, 141, 152, 27, 227, 88, 2, 35, 31, 62, 41, 236, 131, 111, 70, 102, 229, 163, 42, 230, 238, 139, 239, 104, 14, 35, 100, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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