Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2423b9da2877ed1f98a52676a8d5794ab618128d459ac6db610078c2bb83e84

Tx prefix hash: 2eb96eb2b1eb1f9f8f64afd7ecec275d66087a44b2314f2c6b177efc6ba22ec7
Tx public key: 281f81f6a3b4a8d8c7cb520fac5b17b08f6d75506a11eca2ed8420d102777737
Timestamp: 1728186577 Timestamp [UCT]: 2024-10-06 03:49:37 Age [y:d:h:m:s]: 00:207:20:31:14
Block: 1125425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148369 RingCT/type: yes/0
Extra: 01281f81f6a3b4a8d8c7cb520fac5b17b08f6d75506a11eca2ed8420d102777737021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ccaae3dcc92a7c93a1c947583794f3c70be7ff2700d701f0635a150e6a3a7bb 0.600000000000 1608174 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": 1125435, "vin": [ { "gen": { "height": 1125425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ccaae3dcc92a7c93a1c947583794f3c70be7ff2700d701f0635a150e6a3a7bb" } } ], "extra": [ 1, 40, 31, 129, 246, 163, 180, 168, 216, 199, 203, 82, 15, 172, 91, 23, 176, 143, 109, 117, 80, 106, 17, 236, 162, 237, 132, 32, 209, 2, 119, 119, 55, 2, 17, 0, 0, 0, 2, 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