Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e94c164602cad81309cd18c492ef254c9c8dbff43136d3fab7c28403cbcc955d

Tx prefix hash: 54b6cec1b31419200c800c7407f40b23095c3dd917440bca9c6839a288bcad66
Tx public key: 2e51e98113ea1562c770427c650b2e16b2a19b1e7781e8f705855d2798db603b
Timestamp: 1705883358 Timestamp [UCT]: 2024-01-22 00:29:18 Age [y:d:h:m:s]: 01:292:21:12:03
Block: 940495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468142 RingCT/type: yes/0
Extra: 012e51e98113ea1562c770427c650b2e16b2a19b1e7781e8f705855d2798db603b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a1757a0ff7e72a1fafb67fb091c864bcb523c92e268d6b2baf06ad2d92b5a76 0.600000000000 1398633 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": 940505, "vin": [ { "gen": { "height": 940495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a1757a0ff7e72a1fafb67fb091c864bcb523c92e268d6b2baf06ad2d92b5a76" } } ], "extra": [ 1, 46, 81, 233, 129, 19, 234, 21, 98, 199, 112, 66, 124, 101, 11, 46, 22, 178, 161, 155, 30, 119, 129, 232, 247, 5, 133, 93, 39, 152, 219, 96, 59, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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