Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8ad675fd75268c63c3edb2d657d133376619105aa8661c97476830f5b6af58d

Tx prefix hash: b20ffe130461d8dc3c972d86c118f9366407aa2d71b357ce2ff7a11ad08fee4a
Tx public key: f1a7dbcd33e63419893d26a409fe60b83cbf74b08cd451b6c2a3e168a71e53d1
Timestamp: 1717286738 Timestamp [UCT]: 2024-06-02 00:05:38 Age [y:d:h:m:s]: 00:330:14:26:53
Block: 1035067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236297 RingCT/type: yes/0
Extra: 01f1a7dbcd33e63419893d26a409fe60b83cbf74b08cd451b6c2a3e168a71e53d102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91a8404a00ca9b9c21539b60f642c0bb2ab9640cc69e4435a5bc9d174d081c1e 0.600000000000 1503586 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": 1035077, "vin": [ { "gen": { "height": 1035067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91a8404a00ca9b9c21539b60f642c0bb2ab9640cc69e4435a5bc9d174d081c1e" } } ], "extra": [ 1, 241, 167, 219, 205, 51, 230, 52, 25, 137, 61, 38, 164, 9, 254, 96, 184, 60, 191, 116, 176, 140, 212, 81, 182, 194, 163, 225, 104, 167, 30, 83, 209, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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