Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43ce17d9e0d4b13039049879ad1a2ad5d628535d85b291eb9707e98464590e21

Tx prefix hash: 9947effa4e1f6b64af4078b3e4641d2630f4a923488bd663b1a4cd5d8c736942
Tx public key: 54e81f80fd814d57021050e2e0c073156618143b8929ec35c6ac60d11b2d12c4
Timestamp: 1708300214 Timestamp [UCT]: 2024-02-18 23:50:14 Age [y:d:h:m:s]: 01:066:14:16:19
Block: 960561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308642 RingCT/type: yes/0
Extra: 0154e81f80fd814d57021050e2e0c073156618143b8929ec35c6ac60d11b2d12c402110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e31fa6b9a63dabdf3bf6c36d47f44b550e790d9bba8027719d0a275acd9bb373 0.600000000000 1420132 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": 960571, "vin": [ { "gen": { "height": 960561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e31fa6b9a63dabdf3bf6c36d47f44b550e790d9bba8027719d0a275acd9bb373" } } ], "extra": [ 1, 84, 232, 31, 128, 253, 129, 77, 87, 2, 16, 80, 226, 224, 192, 115, 21, 102, 24, 20, 59, 137, 41, 236, 53, 198, 172, 96, 209, 27, 45, 18, 196, 2, 17, 0, 0, 0, 6, 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