Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a20f016bd9dddb15486ea0a6960d3ef6df989fa33f0776564fc3e32b27269b70

Tx prefix hash: 532395ffd75b1f8b28f9fdefd935c75e2f64c729ff071e5c3d67e905f79239f1
Tx public key: 13eed80b1c9b36f389e239b971312099ac021d80f36679d1e0e1f7557ef60516
Timestamp: 1705135361 Timestamp [UCT]: 2024-01-13 08:42:41 Age [y:d:h:m:s]: 01:116:02:16:56
Block: 934294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344109 RingCT/type: yes/0
Extra: 0113eed80b1c9b36f389e239b971312099ac021d80f36679d1e0e1f7557ef6051602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 827132401e94ae73ee7abef3d5d48390518593cc4acd816083d5e6c9f546b703 0.600000000000 1392286 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": 934304, "vin": [ { "gen": { "height": 934294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "827132401e94ae73ee7abef3d5d48390518593cc4acd816083d5e6c9f546b703" } } ], "extra": [ 1, 19, 238, 216, 11, 28, 155, 54, 243, 137, 226, 57, 185, 113, 49, 32, 153, 172, 2, 29, 128, 243, 102, 121, 209, 224, 225, 247, 85, 126, 246, 5, 22, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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