Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aa653820224e11492d180c6dce365c25d685c3a3eb971d52d82229e589a4ccc

Tx prefix hash: 26c7228bf4903f1670f6c876fe7efb71bce155b95d797110f9424141fcf80630
Tx public key: a94ce16f7e2a121bfcc9e736e99b1c2bd07c0a9110b9007e29e15a17070a78fa
Timestamp: 1694019027 Timestamp [UCT]: 2023-09-06 16:50:27 Age [y:d:h:m:s]: 01:117:23:34:12
Block: 842342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345646 RingCT/type: yes/0
Extra: 01a94ce16f7e2a121bfcc9e736e99b1c2bd07c0a9110b9007e29e15a17070a78fa021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.993050533000 dcy

stealth address amount amount idx
00: 1b34fa251e033e48777058dd3d805db52b7cfd7cc76a6fe28e24b344405036f2 0.993050533000 1295458 of 0

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": 842352, "vin": [ { "gen": { "height": 842342 } } ], "vout": [ { "amount": 993050533, "target": { "key": "1b34fa251e033e48777058dd3d805db52b7cfd7cc76a6fe28e24b344405036f2" } } ], "extra": [ 1, 169, 76, 225, 111, 126, 42, 18, 27, 252, 201, 231, 54, 233, 155, 28, 43, 208, 124, 10, 145, 16, 185, 0, 126, 41, 225, 90, 23, 7, 10, 120, 250, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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