Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8ba9edbf4d815b705dafcf5c0d1e25cc47ff3d05c0ce1dd04235effe9d0389a

Tx prefix hash: 6fb07654add6364ec8142dc3536a22c810d7e414edde93a4181d1223d0f3c877
Tx public key: cef8da7ed9920f12c5046f7f18fa77eab32576fa559741a6b943c0b2b547bd95
Timestamp: 1735036798 Timestamp [UCT]: 2024-12-24 10:39:58 Age [y:d:h:m:s]: 00:078:15:45:33
Block: 1182108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55996 RingCT/type: yes/0
Extra: 01cef8da7ed9920f12c5046f7f18fa77eab32576fa559741a6b943c0b2b547bd950211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50e60e437b35d11e543658fe7775300ad80bc2bc73e8a81a81bb32dc8d2dd402 0.600000000000 1668539 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": 1182118, "vin": [ { "gen": { "height": 1182108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50e60e437b35d11e543658fe7775300ad80bc2bc73e8a81a81bb32dc8d2dd402" } } ], "extra": [ 1, 206, 248, 218, 126, 217, 146, 15, 18, 197, 4, 111, 127, 24, 250, 119, 234, 179, 37, 118, 250, 85, 151, 65, 166, 185, 67, 192, 178, 181, 71, 189, 149, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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