Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a2f6f161478c6c3a65e81a8acecfbafb1132e65782b2fac2c503e052d4b0818

Tx prefix hash: 81d16ab0da6d662e737f490ed132575ba905f863995bba44f704f28dd3015494
Tx public key: 5b128f1e22c76cec41ea4f01cc140fcea938123c3a21dcb629ef1fb2b29f6798
Timestamp: 1709150726 Timestamp [UCT]: 2024-02-28 20:05:26 Age [y:d:h:m:s]: 01:043:20:39:28
Block: 967614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292359 RingCT/type: yes/0
Extra: 015b128f1e22c76cec41ea4f01cc140fcea938123c3a21dcb629ef1fb2b29f679802110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89ff29014cb057236e9d39d9302b0227bff7de882c379599f99f14823dba00a1 0.600000000000 1427397 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": 967624, "vin": [ { "gen": { "height": 967614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89ff29014cb057236e9d39d9302b0227bff7de882c379599f99f14823dba00a1" } } ], "extra": [ 1, 91, 18, 143, 30, 34, 199, 108, 236, 65, 234, 79, 1, 204, 20, 15, 206, 169, 56, 18, 60, 58, 33, 220, 182, 41, 239, 31, 178, 178, 159, 103, 152, 2, 17, 0, 0, 0, 11, 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