Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60f7b6c2908d154bac960010cc90a606f5009ec9b972eccf51f09fdf5199cefa

Tx prefix hash: a147a9564bd43a7ca3752781e07fdb39d8a12453d04ea3329c308fc27b67a875
Tx public key: de707747ac577a89e960aa2e5c704a32f3fb4fc0c3dae364d59cd23da1878c3e
Timestamp: 1706583741 Timestamp [UCT]: 2024-01-30 03:02:21 Age [y:d:h:m:s]: 01:095:08:08:34
Block: 946298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329244 RingCT/type: yes/0
Extra: 01de707747ac577a89e960aa2e5c704a32f3fb4fc0c3dae364d59cd23da1878c3e0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0812470ea33a75abd13f8e26257cf03ae9a034e07a5a1d90ce726287ae2d9b9c 0.600000000000 1404630 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": 946308, "vin": [ { "gen": { "height": 946298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0812470ea33a75abd13f8e26257cf03ae9a034e07a5a1d90ce726287ae2d9b9c" } } ], "extra": [ 1, 222, 112, 119, 71, 172, 87, 122, 137, 233, 96, 170, 46, 92, 112, 74, 50, 243, 251, 79, 192, 195, 218, 227, 100, 213, 156, 210, 61, 161, 135, 140, 62, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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