Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c7adb9e96f02d96ff756c8412479c381808acafec48c20b23c44593c1e39dfa

Tx prefix hash: 4749605541c6428d897c95c93a3c1ba972c21f6273e19b6a7e64a02fd1e213dd
Tx public key: 6c197e87d73ad985449e7b3eaf7f0c568e7aecb19143610a85f4df8de81eb2a3
Timestamp: 1695321779 Timestamp [UCT]: 2023-09-21 18:42:59 Age [y:d:h:m:s]: 01:032:09:39:47
Block: 853153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284437 RingCT/type: yes/0
Extra: 016c197e87d73ad985449e7b3eaf7f0c568e7aecb19143610a85f4df8de81eb2a3021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.914429024000 dcy

stealth address amount amount idx
00: aa394fbcb1c4ca5546e5e478331de6ffef73c06236f2f0b93a10b3fdf9bc1cb2 0.914429024000 1307035 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": 853163, "vin": [ { "gen": { "height": 853153 } } ], "vout": [ { "amount": 914429024, "target": { "key": "aa394fbcb1c4ca5546e5e478331de6ffef73c06236f2f0b93a10b3fdf9bc1cb2" } } ], "extra": [ 1, 108, 25, 126, 135, 215, 58, 217, 133, 68, 158, 123, 62, 175, 127, 12, 86, 142, 122, 236, 177, 145, 67, 97, 10, 133, 244, 223, 141, 232, 30, 178, 163, 2, 17, 0, 0, 0, 3, 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