Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 022e0f90b42cb354b61ee11c5fedb4616d23662054886054b073e2ed9af2b57a

Tx prefix hash: 7cdc6c1088326df3c9cb65c5c43dc077ad1f9f0d68b1d743c9fe73d03e2333de
Tx public key: 702986d8e72f2e178ec86eb186e972bd1aed40255093ae2750bf2ad5619e5787
Timestamp: 1706910289 Timestamp [UCT]: 2024-02-02 21:44:49 Age [y:d:h:m:s]: 01:022:12:31:36
Block: 949018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277136 RingCT/type: yes/0
Extra: 01702986d8e72f2e178ec86eb186e972bd1aed40255093ae2750bf2ad5619e578702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c9be4dbc31f1748a6c54674ebe97f11265afde2c4c62d1fb4581c17cbdeb771 0.600000000000 1407540 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": 949028, "vin": [ { "gen": { "height": 949018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c9be4dbc31f1748a6c54674ebe97f11265afde2c4c62d1fb4581c17cbdeb771" } } ], "extra": [ 1, 112, 41, 134, 216, 231, 47, 46, 23, 142, 200, 110, 177, 134, 233, 114, 189, 26, 237, 64, 37, 80, 147, 174, 39, 80, 191, 42, 213, 97, 158, 87, 135, 2, 17, 0, 0, 0, 1, 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