Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e64765a23dad9b3eb74503e746f8d810eccc0a6a5939da3e1c42ff87e5846276

Tx prefix hash: 7fc14e3e52df03a9d99abcc0e8681328b1c0aa084de93cd43f9041ad8e90ff4e
Tx public key: c0a680e6a8c557aae6b38f5bd6ab955e0d9e343b9dbb78dda3aefd85c5824d6d
Timestamp: 1693415811 Timestamp [UCT]: 2023-08-30 17:16:51 Age [y:d:h:m:s]: 01:217:11:15:32
Block: 837347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416534 RingCT/type: yes/0
Extra: 01c0a680e6a8c557aae6b38f5bd6ab955e0d9e343b9dbb78dda3aefd85c5824d6d02110000000b6cce3ea6000000000000000000

1 output(s) for total of 1.031625016000 dcy

stealth address amount amount idx
00: 637632633527025d9191d7d17e24af4e6a480fa74eec5166f9a61f875464585a 1.031625016000 1289969 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": 837357, "vin": [ { "gen": { "height": 837347 } } ], "vout": [ { "amount": 1031625016, "target": { "key": "637632633527025d9191d7d17e24af4e6a480fa74eec5166f9a61f875464585a" } } ], "extra": [ 1, 192, 166, 128, 230, 168, 197, 87, 170, 230, 179, 143, 91, 214, 171, 149, 94, 13, 158, 52, 59, 157, 187, 120, 221, 163, 174, 253, 133, 197, 130, 77, 109, 2, 17, 0, 0, 0, 11, 108, 206, 62, 166, 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