Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 299f3f659dea3c00cd9ead636ab976db832086af422a92c3764ea826e8c4a327

Tx prefix hash: 7ecf5881dcd03f89b5180e727c4e044338c33b24668cb3e2623b62ea65c0b60a
Tx public key: dcd50cfd566d56620021c897aacd11871e9dc91cbed945daf06477cc1fc70eb0
Timestamp: 1706992239 Timestamp [UCT]: 2024-02-03 20:30:39 Age [y:d:h:m:s]: 00:285:07:53:04
Block: 949702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204295 RingCT/type: yes/0
Extra: 01dcd50cfd566d56620021c897aacd11871e9dc91cbed945daf06477cc1fc70eb00211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0ecffc0b249b2b58c2e467e4163542fddb4d94fb53d6ae612fc4c40517d0da8 0.600000000000 1408234 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": 949712, "vin": [ { "gen": { "height": 949702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0ecffc0b249b2b58c2e467e4163542fddb4d94fb53d6ae612fc4c40517d0da8" } } ], "extra": [ 1, 220, 213, 12, 253, 86, 109, 86, 98, 0, 33, 200, 151, 170, 205, 17, 135, 30, 157, 201, 28, 190, 217, 69, 218, 240, 100, 119, 204, 31, 199, 14, 176, 2, 17, 0, 0, 0, 5, 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