Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 802fc4f2b82684a511f71c07e8b0af6c7f81f9d703b26e39d15a9fbe58a0eec5

Tx prefix hash: 808d888333b937335f868fbf53bbc3a3d9b5add55063683bc7e9f1910e7c42c7
Tx public key: 8dee8b83fc79455940f2a8167c983b077df26757e2deabec83b4c3be46118157
Timestamp: 1737239219 Timestamp [UCT]: 2025-01-18 22:26:59 Age [y:d:h:m:s]: 00:332:14:07:05
Block: 1200294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235274 RingCT/type: yes/0
Extra: 018dee8b83fc79455940f2a8167c983b077df26757e2deabec83b4c3be461181570211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14bae803598875d75b0d6bdddcc4df1452e37ae4da444274a2f1016354f90e70 0.600000000000 1686937 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": 1200304, "vin": [ { "gen": { "height": 1200294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14bae803598875d75b0d6bdddcc4df1452e37ae4da444274a2f1016354f90e70" } } ], "extra": [ 1, 141, 238, 139, 131, 252, 121, 69, 89, 64, 242, 168, 22, 124, 152, 59, 7, 125, 242, 103, 87, 226, 222, 171, 236, 131, 180, 195, 190, 70, 17, 129, 87, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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