Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7d332e5a09fedf88d7bdc2881c2f6d16340f7f3891a797be8c86b2a6765892d

Tx prefix hash: 996e587a45181cfcb618669eedb1536021c879518d1158e0ff4f8e1b71fdaea6
Tx public key: 143402ce863a8c518a3f0a63b1e50ba08bcfd6852250fff37e981dcd4919358c
Timestamp: 1723660972 Timestamp [UCT]: 2024-08-14 18:42:52 Age [y:d:h:m:s]: 00:148:09:43:52
Block: 1087912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106151 RingCT/type: yes/0
Extra: 01143402ce863a8c518a3f0a63b1e50ba08bcfd6852250fff37e981dcd4919358c021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fa36c45527d77a78b4b651d1dd31e4d65384886b5a815ab6c15b1cd02fb6257 0.600000000000 1562523 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": 1087922, "vin": [ { "gen": { "height": 1087912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fa36c45527d77a78b4b651d1dd31e4d65384886b5a815ab6c15b1cd02fb6257" } } ], "extra": [ 1, 20, 52, 2, 206, 134, 58, 140, 81, 138, 63, 10, 99, 177, 229, 11, 160, 139, 207, 214, 133, 34, 80, 255, 243, 126, 152, 29, 205, 73, 25, 53, 140, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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