Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bdf23ad2f0a6411203d7fa39bf3b75d358ab9730e026fbf1fca4fed0ee60255

Tx prefix hash: f9c2313606f9fea9c7eb676274f84bbd0d56985ae83e2a994bdc1d63eb7681dc
Tx public key: d68025802725a47870f3647435b64bcc6d59c4d96d95e8f8eb57642a36d8c9c8
Timestamp: 1708840057 Timestamp [UCT]: 2024-02-25 05:47:37 Age [y:d:h:m:s]: 01:046:00:08:41
Block: 965044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293897 RingCT/type: yes/0
Extra: 01d68025802725a47870f3647435b64bcc6d59c4d96d95e8f8eb57642a36d8c9c80211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d3500185d15620514340d8d13b897ed402f1c609eac96cf6f3e80a66bf64ef2 0.600000000000 1424791 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": 965054, "vin": [ { "gen": { "height": 965044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d3500185d15620514340d8d13b897ed402f1c609eac96cf6f3e80a66bf64ef2" } } ], "extra": [ 1, 214, 128, 37, 128, 39, 37, 164, 120, 112, 243, 100, 116, 53, 182, 75, 204, 109, 89, 196, 217, 109, 149, 232, 248, 235, 87, 100, 42, 54, 216, 201, 200, 2, 17, 0, 0, 0, 6, 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