Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4325395efc238b4d012e589b5ecd9adf0198c89fa6d46bc5f9caaa5cf82b9ade

Tx prefix hash: 95d753f03a7c893299ef778d90440eb64bae4ebc63c88ff4596b331fe1256451
Tx public key: adfa0061edaee9562e443d4fe645316b2d3ad90fd873e180f2a91cf50087b8e9
Timestamp: 1680947542 Timestamp [UCT]: 2023-04-08 09:52:22 Age [y:d:h:m:s]: 02:037:12:39:35
Block: 734174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548871 RingCT/type: yes/0
Extra: 01adfa0061edaee9562e443d4fe645316b2d3ad90fd873e180f2a91cf50087b8e9021100000010b3164c24000000000000000000

1 output(s) for total of 2.266671011000 dcy

stealth address amount amount idx
00: 4567a682673c2f63b8d4c02d059785f1a36aea8ae328ad3de60f0369cfa5d0a9 2.266671011000 1180335 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": 734184, "vin": [ { "gen": { "height": 734174 } } ], "vout": [ { "amount": 2266671011, "target": { "key": "4567a682673c2f63b8d4c02d059785f1a36aea8ae328ad3de60f0369cfa5d0a9" } } ], "extra": [ 1, 173, 250, 0, 97, 237, 174, 233, 86, 46, 68, 61, 79, 230, 69, 49, 107, 45, 58, 217, 15, 216, 115, 225, 128, 242, 169, 28, 245, 0, 135, 184, 233, 2, 17, 0, 0, 0, 16, 179, 22, 76, 36, 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