Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e236e7ddcabc2c1a608c763442513856c836697f0cfa551a50810cb9e6f8fae0

Tx prefix hash: 2427d63bc9d33ffe7ec5da973db6a6f78f0742fe51bcc451957ea2bbf436165d
Tx public key: ad7363b380a8700b8ce838b3aa3b52bb6cda226efd9945326c423af92fcea802
Timestamp: 1698075749 Timestamp [UCT]: 2023-10-23 15:42:29 Age [y:d:h:m:s]: 01:092:01:15:03
Block: 875992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326988 RingCT/type: yes/0
Extra: 01ad7363b380a8700b8ce838b3aa3b52bb6cda226efd9945326c423af92fcea80202110000000875e3f0e9000000000000000000

1 output(s) for total of 0.768201023000 dcy

stealth address amount amount idx
00: c78eda8c93c45c1a4879e7516d401f4e727e226c3aedcbe5201ce774ae5db03d 0.768201023000 1331298 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": 876002, "vin": [ { "gen": { "height": 875992 } } ], "vout": [ { "amount": 768201023, "target": { "key": "c78eda8c93c45c1a4879e7516d401f4e727e226c3aedcbe5201ce774ae5db03d" } } ], "extra": [ 1, 173, 115, 99, 179, 128, 168, 112, 11, 140, 232, 56, 179, 170, 59, 82, 187, 108, 218, 34, 110, 253, 153, 69, 50, 108, 66, 58, 249, 47, 206, 168, 2, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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