Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f763aa5793c50f42e976ca44602bcc120fb560156cdb8b2c250674bf2744feaa

Tx prefix hash: 3da73e27de3d5937dad15be8b3d9afe3d9c59bdc4a8216bcaebfb3f0fdabdd31
Tx public key: 03b52b264b662415078d8c0ef1028eb9a8c0a8d5e567ea752b3ffb3b32efceb0
Timestamp: 1714103675 Timestamp [UCT]: 2024-04-26 03:54:35 Age [y:d:h:m:s]: 00:346:15:23:11
Block: 1008667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247793 RingCT/type: yes/0
Extra: 0103b52b264b662415078d8c0ef1028eb9a8c0a8d5e567ea752b3ffb3b32efceb002110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7744f1fa5dbb90ae713c488748dff6634cdf7af61e0a2b1db35bc704f716b43a 0.600000000000 1470143 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": 1008677, "vin": [ { "gen": { "height": 1008667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7744f1fa5dbb90ae713c488748dff6634cdf7af61e0a2b1db35bc704f716b43a" } } ], "extra": [ 1, 3, 181, 43, 38, 75, 102, 36, 21, 7, 141, 140, 14, 241, 2, 142, 185, 168, 192, 168, 213, 229, 103, 234, 117, 43, 63, 251, 59, 50, 239, 206, 176, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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