Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c208399aabbeb549df80d7cb7d0f3eba2b2d0901bf6ec973dd1f75679232bb6

Tx prefix hash: 6f23e73537dd93ce5fedd8634ed6bda34ab6bd3c1152e290889a1fab9840cfcc
Tx public key: b9f9a2e489b07951ac91e2ef7b85afd07edc911306f9571384baf3ef77c6abbe
Timestamp: 1705787053 Timestamp [UCT]: 2024-01-20 21:44:13 Age [y:d:h:m:s]: 01:096:09:00:27
Block: 939688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330003 RingCT/type: yes/0
Extra: 01b9f9a2e489b07951ac91e2ef7b85afd07edc911306f9571384baf3ef77c6abbe0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45b3fe9888c0e903df71a8d7d9ff747b872304b15cfe93cb51de37a1a8f9e640 0.600000000000 1397800 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": 939698, "vin": [ { "gen": { "height": 939688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45b3fe9888c0e903df71a8d7d9ff747b872304b15cfe93cb51de37a1a8f9e640" } } ], "extra": [ 1, 185, 249, 162, 228, 137, 176, 121, 81, 172, 145, 226, 239, 123, 133, 175, 208, 126, 220, 145, 19, 6, 249, 87, 19, 132, 186, 243, 239, 119, 198, 171, 190, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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