Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30cc94df87b9ab32a63d47a80d683f71ff87265d2e1185fbf7febb7a0ae5b844

Tx prefix hash: c3ea80a14d0bd049eb0d94f1c10d8102f921af7db7630d5df10af532678041d2
Tx public key: 7d2ee999b2d8afcbb4418611d3d988a470cd2eda0ab10cad91df4a0b64ab760d
Timestamp: 1713623225 Timestamp [UCT]: 2024-04-20 14:27:05 Age [y:d:h:m:s]: 00:224:20:29:56
Block: 1004676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160983 RingCT/type: yes/0
Extra: 017d2ee999b2d8afcbb4418611d3d988a470cd2eda0ab10cad91df4a0b64ab760d0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d57618867856423bf8f3685d66bd4c654ed355f4e0b262229822be338c523cab 0.600000000000 1465246 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": 1004686, "vin": [ { "gen": { "height": 1004676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d57618867856423bf8f3685d66bd4c654ed355f4e0b262229822be338c523cab" } } ], "extra": [ 1, 125, 46, 233, 153, 178, 216, 175, 203, 180, 65, 134, 17, 211, 217, 136, 164, 112, 205, 46, 218, 10, 177, 12, 173, 145, 223, 74, 11, 100, 171, 118, 13, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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