Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02e0d6487b8c046dac2c43872608f9caa617fc3050a5943897bceabcfccde4e0

Tx prefix hash: 52126bf9a17b796bce2730f21d58b8892cfdd0f50e511d1c9dc5e352c46a8921
Tx public key: a11b74aa8e56d6cb88f38c44a547a7b76881e94e1b6c3e5003b7491554cccb94
Timestamp: 1698333583 Timestamp [UCT]: 2023-10-26 15:19:43 Age [y:d:h:m:s]: 01:087:10:06:27
Block: 878147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323660 RingCT/type: yes/0
Extra: 01a11b74aa8e56d6cb88f38c44a547a7b76881e94e1b6c3e5003b7491554cccb94021100000001faf35c9c000000000000000000

1 output(s) for total of 0.755673980000 dcy

stealth address amount amount idx
00: f83d1e8dc8ff73dd5d0eb370944eecaadef49b0646b886796843db6fcd306c4a 0.755673980000 1333563 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": 878157, "vin": [ { "gen": { "height": 878147 } } ], "vout": [ { "amount": 755673980, "target": { "key": "f83d1e8dc8ff73dd5d0eb370944eecaadef49b0646b886796843db6fcd306c4a" } } ], "extra": [ 1, 161, 27, 116, 170, 142, 86, 214, 203, 136, 243, 140, 68, 165, 71, 167, 183, 104, 129, 233, 78, 27, 108, 62, 80, 3, 183, 73, 21, 84, 204, 203, 148, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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