Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60a68328a19978569c312cbc2a28d926cbb4c84603960b35740fa07278db377d

Tx prefix hash: 9cba1bec2283a272fe853e5b0e2c9d2f31fcb0ea5e65b4d9598c2118219d9e4e
Tx public key: d1249d8d5996a7435768d07df9cbdf80adf8407336b367746a18ac309c9f169b
Timestamp: 1673257248 Timestamp [UCT]: 2023-01-09 09:40:48 Age [y:d:h:m:s]: 02:092:02:59:28
Block: 670888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587534 RingCT/type: yes/0
Extra: 01d1249d8d5996a7435768d07df9cbdf80adf8407336b367746a18ac309c9f169b021100000002b3e1cbca000000000000000000

1 output(s) for total of 3.673410923000 dcy

stealth address amount amount idx
00: 25ef1f8b9cbf4294a23091a2a43751c2d1f85b64f96f4e1d6e200cbb4f3902cc 3.673410923000 1112313 of 0

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": 670898, "vin": [ { "gen": { "height": 670888 } } ], "vout": [ { "amount": 3673410923, "target": { "key": "25ef1f8b9cbf4294a23091a2a43751c2d1f85b64f96f4e1d6e200cbb4f3902cc" } } ], "extra": [ 1, 209, 36, 157, 141, 89, 150, 167, 67, 87, 104, 208, 125, 249, 203, 223, 128, 173, 248, 64, 115, 54, 179, 103, 116, 106, 24, 172, 48, 156, 159, 22, 155, 2, 17, 0, 0, 0, 2, 179, 225, 203, 202, 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