Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcc80362c47e16f7cc57e9eafcb334ebcbaa8374373c4ba986a6e69394345ff2

Tx prefix hash: 33be27ba9bfde99295b6afb6fbd0a8046c71b5cc955d071aef6bc4cbbe9f0eaa
Tx public key: d744d5320f0abffac3c92de1643fb40589ea85b2e539f1c7e61cf7a391b19a45
Timestamp: 1635605637 Timestamp [UCT]: 2021-10-30 14:53:57 Age [y:d:h:m:s]: 03:100:04:14:21
Block: 363698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 849862 RingCT/type: yes/0
Extra: 01d744d5320f0abffac3c92de1643fb40589ea85b2e539f1c7e61cf7a391b19a4502110000000b42b3953e000000000000000000

1 output(s) for total of 38.275242532000 dcy

stealth address amount amount idx
00: ad96edce7a9d0bd0d7dbba72b2a2d0be03df28c0ba838b3dac821f0c60f69457 38.275242532000 739110 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": 363708, "vin": [ { "gen": { "height": 363698 } } ], "vout": [ { "amount": 38275242532, "target": { "key": "ad96edce7a9d0bd0d7dbba72b2a2d0be03df28c0ba838b3dac821f0c60f69457" } } ], "extra": [ 1, 215, 68, 213, 50, 15, 10, 191, 250, 195, 201, 45, 225, 100, 63, 180, 5, 137, 234, 133, 178, 229, 57, 241, 199, 230, 28, 247, 163, 145, 177, 154, 69, 2, 17, 0, 0, 0, 11, 66, 179, 149, 62, 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