Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f0c3e8dd96d616eb69d0d797d67daea526fe4906134e6dbd199d85771fda368

Tx prefix hash: a57c50bf6eb3ba677a9f08c56070a834f93416326f4dd0f8149be567f5151a31
Tx public key: 5a2cf88a4038c86882b4540ceaefb7ecf60f82638a4f345b1109b5b08265a71a
Timestamp: 1636962044 Timestamp [UCT]: 2021-11-15 07:40:44 Age [y:d:h:m:s]: 03:012:09:50:54
Block: 374676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 787595 RingCT/type: yes/0
Extra: 015a2cf88a4038c86882b4540ceaefb7ecf60f82638a4f345b1109b5b08265a71a021100000001a272b9cb000000000000000000

1 output(s) for total of 35.200658676000 dcy

stealth address amount amount idx
00: 86d5cafad86cfe0dd6ab13ecd095c5afc223cd16905c82e82c9ace0c958023c2 35.200658676000 758314 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": 374686, "vin": [ { "gen": { "height": 374676 } } ], "vout": [ { "amount": 35200658676, "target": { "key": "86d5cafad86cfe0dd6ab13ecd095c5afc223cd16905c82e82c9ace0c958023c2" } } ], "extra": [ 1, 90, 44, 248, 138, 64, 56, 200, 104, 130, 180, 84, 12, 234, 239, 183, 236, 246, 15, 130, 99, 138, 79, 52, 91, 17, 9, 181, 176, 130, 101, 167, 26, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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