Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7af483a8eea43601dfcf03a48cc73dfbb006a67a8d5092f18b5e383a3e998337

Tx prefix hash: a40579a4bc95a9dda9aa5a24b6c4e031ad64df4866b2570254b1d9b602f3ba4d
Tx public key: 9cc025747e055cc35085dd8e7ee79aa9c00e51e52283935485806a02ec31fb59
Timestamp: 1706755259 Timestamp [UCT]: 2024-02-01 02:40:59 Age [y:d:h:m:s]: 00:361:03:24:57
Block: 947731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258312 RingCT/type: yes/0
Extra: 019cc025747e055cc35085dd8e7ee79aa9c00e51e52283935485806a02ec31fb5902110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3c0d5b3f992fddaf5747c24621a31b1e2ce66dce553abf19b2adab73032e8a2 0.600000000000 1406089 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": 947741, "vin": [ { "gen": { "height": 947731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3c0d5b3f992fddaf5747c24621a31b1e2ce66dce553abf19b2adab73032e8a2" } } ], "extra": [ 1, 156, 192, 37, 116, 126, 5, 92, 195, 80, 133, 221, 142, 126, 231, 154, 169, 192, 14, 81, 229, 34, 131, 147, 84, 133, 128, 106, 2, 236, 49, 251, 89, 2, 17, 0, 0, 0, 5, 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