Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d121e2b3574e4bcee6c8f201b141f50bc0038a23b9267e926e0b82b6d97f64a9

Tx prefix hash: 0eaff7910535da5194bc730a128d441161435cfaabef93383e0c4bda8ebed1cc
Tx public key: eb9df644c149ed6fd1020698d5a4e22a1a576535ce0e87e111f0475cc881c111
Timestamp: 1706889826 Timestamp [UCT]: 2024-02-02 16:03:46 Age [y:d:h:m:s]: 00:347:18:14:26
Block: 948853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248960 RingCT/type: yes/0
Extra: 01eb9df644c149ed6fd1020698d5a4e22a1a576535ce0e87e111f0475cc881c11102110000000310a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6acfe4d8a84e552c17c739b41d2e47aaceb0b810b86cff2dd2e2867dae5c403c 0.600000000000 1407353 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": 948863, "vin": [ { "gen": { "height": 948853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6acfe4d8a84e552c17c739b41d2e47aaceb0b810b86cff2dd2e2867dae5c403c" } } ], "extra": [ 1, 235, 157, 246, 68, 193, 73, 237, 111, 209, 2, 6, 152, 213, 164, 226, 42, 26, 87, 101, 53, 206, 14, 135, 225, 17, 240, 71, 92, 200, 129, 193, 17, 2, 17, 0, 0, 0, 3, 16, 161, 116, 143, 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