Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4e743f28b20642322054f68331e57a6f28b392a13dbea0a72436fd825837567

Tx prefix hash: 8f93b544bf652c39d60bf0cf79939ac15bd8e2903ceae0ccec5a393d773efd94
Tx public key: de8a747fa3b1ef5a518634934e0ab91a6230776cbe8297f1cf9d0e39ddb966b1
Timestamp: 1710589753 Timestamp [UCT]: 2024-03-16 11:49:13 Age [y:d:h:m:s]: 00:344:08:44:17
Block: 979560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246174 RingCT/type: yes/0
Extra: 01de8a747fa3b1ef5a518634934e0ab91a6230776cbe8297f1cf9d0e39ddb966b102110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f40fbd7d4272e8a8e2b744c28212a0ff89323d0ac00d4efdc897c493b006e71a 0.600000000000 1439597 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": 979570, "vin": [ { "gen": { "height": 979560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f40fbd7d4272e8a8e2b744c28212a0ff89323d0ac00d4efdc897c493b006e71a" } } ], "extra": [ 1, 222, 138, 116, 127, 163, 177, 239, 90, 81, 134, 52, 147, 78, 10, 185, 26, 98, 48, 119, 108, 190, 130, 151, 241, 207, 157, 14, 57, 221, 185, 102, 177, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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