Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e39b032adbdfb02fd002372085fb04eec3396ca6238b5b2408c1a61a444ec912

Tx prefix hash: 39bcf033d2afe67d325d83cd8377bb5912d9e4f4ac874b5f4ab9e27010c8a3a7
Tx public key: 49bc0e80a7244d8cca92dc7340bbcc243429a575afdf896fe2561ddabe4a178f
Timestamp: 1709866877 Timestamp [UCT]: 2024-03-08 03:01:17 Age [y:d:h:m:s]: 01:246:19:03:58
Block: 973553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435104 RingCT/type: yes/0
Extra: 0149bc0e80a7244d8cca92dc7340bbcc243429a575afdf896fe2561ddabe4a178f02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68adadf25a01c32b804e8880bf93d09d8176e1b24b034b0bf401bf0b2ce2073f 0.600000000000 1433488 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": 973563, "vin": [ { "gen": { "height": 973553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68adadf25a01c32b804e8880bf93d09d8176e1b24b034b0bf401bf0b2ce2073f" } } ], "extra": [ 1, 73, 188, 14, 128, 167, 36, 77, 140, 202, 146, 220, 115, 64, 187, 204, 36, 52, 41, 165, 117, 175, 223, 137, 111, 226, 86, 29, 218, 190, 74, 23, 143, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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