Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af22d6eecaabdc1ecadb2928c966e88bb379512cd6a375568b9b074f9a3262ef

Tx prefix hash: e0b3aa6017a1e8f71504a62f5c917b7074627f96e9072e83494d1a9c1ff77e8f
Tx public key: 432e21818dcc60854b5ca397278f18ad1ded0b166b8448b0a7df8893023610d1
Timestamp: 1712659411 Timestamp [UCT]: 2024-04-09 10:43:31 Age [y:d:h:m:s]: 00:218:23:26:17
Block: 996679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156779 RingCT/type: yes/0
Extra: 01432e21818dcc60854b5ca397278f18ad1ded0b166b8448b0a7df8893023610d10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1972708d50960d929286d6f408937ec93d17d85d192ff37a964f396a6c6e5ed7 0.600000000000 1457105 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": 996689, "vin": [ { "gen": { "height": 996679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1972708d50960d929286d6f408937ec93d17d85d192ff37a964f396a6c6e5ed7" } } ], "extra": [ 1, 67, 46, 33, 129, 141, 204, 96, 133, 75, 92, 163, 151, 39, 143, 24, 173, 29, 237, 11, 22, 107, 132, 72, 176, 167, 223, 136, 147, 2, 54, 16, 209, 2, 17, 0, 0, 0, 1, 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