Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a02db7a0cc7cd12fa38111e6a38f6e6deaf20e90bba755a22b121dfd90dee003

Tx prefix hash: aaba2708b533496fbb714a6aa1ff76400dc2fac0a43f1342708cbe96c97c90e4
Tx public key: 755a6f7426d87aa931c3da8fb7dab1d373546ab79e50cc63301a12fce4cf7d0b
Timestamp: 1707507247 Timestamp [UCT]: 2024-02-09 19:34:07 Age [y:d:h:m:s]: 01:129:11:24:13
Block: 953969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353525 RingCT/type: yes/0
Extra: 01755a6f7426d87aa931c3da8fb7dab1d373546ab79e50cc63301a12fce4cf7d0b021100000002ec57b234000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08f065deae242b2febf451c693b7be607208ff54e2d18834fc599c547636e1b9 0.600000000000 1413241 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": 953979, "vin": [ { "gen": { "height": 953969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08f065deae242b2febf451c693b7be607208ff54e2d18834fc599c547636e1b9" } } ], "extra": [ 1, 117, 90, 111, 116, 38, 216, 122, 169, 49, 195, 218, 143, 183, 218, 177, 211, 115, 84, 106, 183, 158, 80, 204, 99, 48, 26, 18, 252, 228, 207, 125, 11, 2, 17, 0, 0, 0, 2, 236, 87, 178, 52, 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