Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad815fee289d74c435fdb09c92c6e3ce39e9961b7c6b5691d85226d00eddd6f0

Tx prefix hash: 1d5fea6cc83c4fd6c70239b1014a03acceb2dfccb8bea360cfb791a9d17ddcf1
Tx public key: dc7510eb379598e211b67731e9c9d4fe9722353a9da6b0d09ca4eca6314197c5
Timestamp: 1734319470 Timestamp [UCT]: 2024-12-16 03:24:30 Age [y:d:h:m:s]: 00:096:12:33:23
Block: 1176180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68763 RingCT/type: yes/0
Extra: 01dc7510eb379598e211b67731e9c9d4fe9722353a9da6b0d09ca4eca6314197c50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad84c9cae4a2b561ee27ca64e3399c6d6075467adcc3c567da6684d49a62b07f 0.600000000000 1662511 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": 1176190, "vin": [ { "gen": { "height": 1176180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad84c9cae4a2b561ee27ca64e3399c6d6075467adcc3c567da6684d49a62b07f" } } ], "extra": [ 1, 220, 117, 16, 235, 55, 149, 152, 226, 17, 182, 119, 49, 233, 201, 212, 254, 151, 34, 53, 58, 157, 166, 176, 208, 156, 164, 236, 166, 49, 65, 151, 197, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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