Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce8239c5d3dcd1c24ec9c949b362175a20ec47d368293138a16b605ddb025d67

Tx prefix hash: 526085ba440b814fd9e11236ed0076eeb6518ca59017a217cb02a9c4feab2b49
Tx public key: d17fa5159c9fea3ec4b7f4d35f61f7a7681c596870248fbaa0aa2255fdfc2bc5
Timestamp: 1701480909 Timestamp [UCT]: 2023-12-02 01:35:09 Age [y:d:h:m:s]: 01:345:04:48:45
Block: 904012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505594 RingCT/type: yes/0
Extra: 01d17fa5159c9fea3ec4b7f4d35f61f7a7681c596870248fbaa0aa2255fdfc2bc5021100000002faf35c9c000000000000000000

1 output(s) for total of 0.620344517000 dcy

stealth address amount amount idx
00: b3c9fca0d1daaed9c50e772456d0765d8579e41dfb474b9c0e3531c0d31ba0a3 0.620344517000 1360715 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": 904022, "vin": [ { "gen": { "height": 904012 } } ], "vout": [ { "amount": 620344517, "target": { "key": "b3c9fca0d1daaed9c50e772456d0765d8579e41dfb474b9c0e3531c0d31ba0a3" } } ], "extra": [ 1, 209, 127, 165, 21, 156, 159, 234, 62, 196, 183, 244, 211, 95, 97, 247, 167, 104, 28, 89, 104, 112, 36, 143, 186, 160, 170, 34, 85, 253, 252, 43, 197, 2, 17, 0, 0, 0, 2, 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