Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4039e8f85d63da2f95bc7f8b02f1625c3c3fe630d939eb4b3ea7a3bf22f606b5

Tx prefix hash: 077db000b444f4c6f8f8f2d50aaceec7babd5c151dd2438f892dd51ffed1e7b2
Tx public key: 014b6abf3cf27076aa3241c72e73ef1882bd5b61542f32cab377ae3bacc080e2
Timestamp: 1685064200 Timestamp [UCT]: 2023-05-26 01:23:20 Age [y:d:h:m:s]: 01:237:22:13:05
Block: 768166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431481 RingCT/type: yes/0
Extra: 01014b6abf3cf27076aa3241c72e73ef1882bd5b61542f32cab377ae3bacc080e202110000000333af99f4000000000000000000

1 output(s) for total of 1.748828965000 dcy

stealth address amount amount idx
00: 06abe1094703aaefb3332b4a280a57dea13150043471f06a522005a98fb7c929 1.748828965000 1217357 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": 768176, "vin": [ { "gen": { "height": 768166 } } ], "vout": [ { "amount": 1748828965, "target": { "key": "06abe1094703aaefb3332b4a280a57dea13150043471f06a522005a98fb7c929" } } ], "extra": [ 1, 1, 75, 106, 191, 60, 242, 112, 118, 170, 50, 65, 199, 46, 115, 239, 24, 130, 189, 91, 97, 84, 47, 50, 202, 179, 119, 174, 59, 172, 192, 128, 226, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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