Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08bfd453fc298165084331c5a6cdec8ae5ecd1a27df34d6f945eaaddc44822ef

Tx prefix hash: d5eae0cbbb5066039ec53a60ddc960c0b8ca22ed7ae43187f82d6a14ed37a9f2
Tx public key: 1701432f60e1bd6ea294c7d2bb7ebc3f13d7e985e6de8365605f1209460bb189
Timestamp: 1710963249 Timestamp [UCT]: 2024-03-20 19:34:09 Age [y:d:h:m:s]: 01:257:09:33:10
Block: 982654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442670 RingCT/type: yes/0
Extra: 011701432f60e1bd6ea294c7d2bb7ebc3f13d7e985e6de8365605f1209460bb18902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 062d8907d8303dc0259324365abbccc1e1f3aa124fb9922b2c63190e0161b6b2 0.600000000000 1442763 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": 982664, "vin": [ { "gen": { "height": 982654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "062d8907d8303dc0259324365abbccc1e1f3aa124fb9922b2c63190e0161b6b2" } } ], "extra": [ 1, 23, 1, 67, 47, 96, 225, 189, 110, 162, 148, 199, 210, 187, 126, 188, 63, 19, 215, 233, 133, 230, 222, 131, 101, 96, 95, 18, 9, 70, 11, 177, 137, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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