Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2d24e400cc96a37dc0b4da5dd233145db232eeccde6236da49a87cbbcb99d1f

Tx prefix hash: 79644087ee827a0097867238c2595e5873b9fd9068a90ef9b13eff18ea912a1c
Tx public key: 5efd4cdea9e2c3df65ad6ca27998dc6f751026dec6b170c1d1a02c07a0a2f24e
Timestamp: 1726167202 Timestamp [UCT]: 2024-09-12 18:53:22 Age [y:d:h:m:s]: 00:119:12:56:15
Block: 1108681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85485 RingCT/type: yes/0
Extra: 015efd4cdea9e2c3df65ad6ca27998dc6f751026dec6b170c1d1a02c07a0a2f24e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0b1c3eebfcd905fadfb68c4f5aaf6d816b0435b9194025ea84509d7fdde2c96 0.600000000000 1586662 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": 1108691, "vin": [ { "gen": { "height": 1108681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0b1c3eebfcd905fadfb68c4f5aaf6d816b0435b9194025ea84509d7fdde2c96" } } ], "extra": [ 1, 94, 253, 76, 222, 169, 226, 195, 223, 101, 173, 108, 162, 121, 152, 220, 111, 117, 16, 38, 222, 198, 177, 112, 193, 209, 160, 44, 7, 160, 162, 242, 78, 2, 17, 0, 0, 0, 3, 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