Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e6b0fc65f10e1e86b7085291467fbc01c4792727576a1fa89d0b4cc173fcf94

Tx prefix hash: 47e74b34a976c9596aab297d85d714629ebfc46379b0d57e545d392c5ff161b8
Tx public key: af9d20dbef3d6f05e4cbb3a0d267714a064cd18e87c86c155a044909ca41c6df
Timestamp: 1734463388 Timestamp [UCT]: 2024-12-17 19:23:08 Age [y:d:h:m:s]: 00:120:17:07:14
Block: 1177375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86046 RingCT/type: yes/0
Extra: 01af9d20dbef3d6f05e4cbb3a0d267714a064cd18e87c86c155a044909ca41c6df0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a875b7e22495493eed64ae3f393c55bc1b48904fe654ea495573364be0ecf49 0.600000000000 1663746 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": 1177385, "vin": [ { "gen": { "height": 1177375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a875b7e22495493eed64ae3f393c55bc1b48904fe654ea495573364be0ecf49" } } ], "extra": [ 1, 175, 157, 32, 219, 239, 61, 111, 5, 228, 203, 179, 160, 210, 103, 113, 74, 6, 76, 209, 142, 135, 200, 108, 21, 90, 4, 73, 9, 202, 65, 198, 223, 2, 17, 0, 0, 0, 5, 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