Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4325db09637eaa2d12b78f1bdbc62a2d9500163e6dd9bd60b711f1d203345aae

Tx prefix hash: 48ab422c2b98879b4f34d87825dfcea81d6931a73edbf3cf9264147a1c941971
Tx public key: 3905b934e2e7de8ca8424953dcb3b2c13c5bf187163b64f17d5b93d0601382b9
Timestamp: 1727114142 Timestamp [UCT]: 2024-09-23 17:55:42 Age [y:d:h:m:s]: 00:108:01:44:31
Block: 1116532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77275 RingCT/type: yes/0
Extra: 013905b934e2e7de8ca8424953dcb3b2c13c5bf187163b64f17d5b93d0601382b9021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94722681c6fbd9033e2ba4ab761690992d4add1bd4d11caac523e917e880a34a 0.600000000000 1597051 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": 1116542, "vin": [ { "gen": { "height": 1116532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94722681c6fbd9033e2ba4ab761690992d4add1bd4d11caac523e917e880a34a" } } ], "extra": [ 1, 57, 5, 185, 52, 226, 231, 222, 140, 168, 66, 73, 83, 220, 179, 178, 193, 60, 91, 241, 135, 22, 59, 100, 241, 125, 91, 147, 208, 96, 19, 130, 185, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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