Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfcf42005985ef37953475ce19665de27a7e0ea51153f9c9aa496704d28a0a0e

Tx prefix hash: a7f22851b787f4234c274ab67f1da1c1e9f4007f3aa849622f0a9bc39bee66b3
Tx public key: 686967361d8e09884bf8f46c37d9b3135f1cada37f9651bb19fd9ab17c0dad1f
Timestamp: 1625036427 Timestamp [UCT]: 2021-06-30 07:00:27 Age [y:d:h:m:s]: 03:098:07:20:39
Block: 285747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 839273 RingCT/type: yes/0
Extra: 01686967361d8e09884bf8f46c37d9b3135f1cada37f9651bb19fd9ab17c0dad1f02110000000d3a645b90000000000000000000

1 output(s) for total of 69.374853793000 dcy

stealth address amount amount idx
00: 4b4e42d863dc15e66dbf4be125ae90e9e53da01b608e47e4166f2decc1d310ef 69.374853793000 598366 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": 285757, "vin": [ { "gen": { "height": 285747 } } ], "vout": [ { "amount": 69374853793, "target": { "key": "4b4e42d863dc15e66dbf4be125ae90e9e53da01b608e47e4166f2decc1d310ef" } } ], "extra": [ 1, 104, 105, 103, 54, 29, 142, 9, 136, 75, 248, 244, 108, 55, 217, 179, 19, 95, 28, 173, 163, 127, 150, 81, 187, 25, 253, 154, 177, 124, 13, 173, 31, 2, 17, 0, 0, 0, 13, 58, 100, 91, 144, 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