Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d50d6023607098bcd8398b0713acb81a5afbb8d31ffffdb0e2750ffa6ce03bae

Tx prefix hash: 66b9e593a81b354b3612a93126aea4f46c79ebcaee337da7c6b9804be5fabcd6
Tx public key: 0c6b1eaaedf5131dd2e5d89534fbefa2d39742519e5ec8ec1e02164b1992b407
Timestamp: 1733754753 Timestamp [UCT]: 2024-12-09 14:32:33 Age [y:d:h:m:s]: 00:139:23:41:11
Block: 1171493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99860 RingCT/type: yes/0
Extra: 010c6b1eaaedf5131dd2e5d89534fbefa2d39742519e5ec8ec1e02164b1992b407021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba830df9ea6134be43726139116afaf2b866534fa3865a7a9c1e4e3463165f5e 0.600000000000 1657256 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": 1171503, "vin": [ { "gen": { "height": 1171493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba830df9ea6134be43726139116afaf2b866534fa3865a7a9c1e4e3463165f5e" } } ], "extra": [ 1, 12, 107, 30, 170, 237, 245, 19, 29, 210, 229, 216, 149, 52, 251, 239, 162, 211, 151, 66, 81, 158, 94, 200, 236, 30, 2, 22, 75, 25, 146, 180, 7, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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