Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 412f609955803d0b8edf65c3c00843b6fcb2a9a26fcfb8bbdb737184f46c75c7

Tx prefix hash: 65bce4e53e00c8c9e99bc9890466e3c22d9cc06827e592d8254657ff49442df0
Tx public key: a52338fbf04a0ef5450da1ee1bb36b579ba5b7324fa9575e0481a2643e1dc0eb
Timestamp: 1707732648 Timestamp [UCT]: 2024-02-12 10:10:48 Age [y:d:h:m:s]: 00:314:10:26:48
Block: 955848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225150 RingCT/type: yes/0
Extra: 01a52338fbf04a0ef5450da1ee1bb36b579ba5b7324fa9575e0481a2643e1dc0eb02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ebc788de3f46d00e589d071f60b3cb7d58db5e08a2a66d45fb4353af0744b64 0.600000000000 1415148 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": 955858, "vin": [ { "gen": { "height": 955848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ebc788de3f46d00e589d071f60b3cb7d58db5e08a2a66d45fb4353af0744b64" } } ], "extra": [ 1, 165, 35, 56, 251, 240, 74, 14, 245, 69, 13, 161, 238, 27, 179, 107, 87, 155, 165, 183, 50, 79, 169, 87, 94, 4, 129, 162, 100, 62, 29, 192, 235, 2, 17, 0, 0, 0, 8, 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