Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c3c26dd8afdbeea6f137b6f9e2c5e71f71cc4b3c7f690998930cf4e9b05627c

Tx prefix hash: fc62cb9cba3f6d304dba07a8d59d5e61f700bd502573071a18c971f0b30284a3
Tx public key: 4ad3574b348c9851170acc9986799457a598ea2562f96a40ed63d01c0fa7d73d
Timestamp: 1729775139 Timestamp [UCT]: 2024-10-24 13:05:39 Age [y:d:h:m:s]: 00:090:05:12:04
Block: 1138557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64470 RingCT/type: yes/0
Extra: 014ad3574b348c9851170acc9986799457a598ea2562f96a40ed63d01c0fa7d73d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64c22c53e524d2b646321993216449dedfca1ad077e86be7d2b2aab0620ccbf2 0.600000000000 1622244 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": 1138567, "vin": [ { "gen": { "height": 1138557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64c22c53e524d2b646321993216449dedfca1ad077e86be7d2b2aab0620ccbf2" } } ], "extra": [ 1, 74, 211, 87, 75, 52, 140, 152, 81, 23, 10, 204, 153, 134, 121, 148, 87, 165, 152, 234, 37, 98, 249, 106, 64, 237, 99, 208, 28, 15, 167, 215, 61, 2, 17, 0, 0, 0, 3, 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