← previous blocknext block →recent activity

Analyzing

Block #92,974,993

17 transactions · 17 stateful · 2026-08-04 05:16:14 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,974,993  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x3de775b2…319b

0xa6afd3…d132

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xfa551be3…a911

0xa6afd3…d132

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0d488000…3831

0x34b655…2a6f

4 touches
1 conflict

0x6bf71f68…fd07

0x34b655…2a6f

4 touches
1 conflict

0xd1b40f29…9b9d

0x34b655…2a6f

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Kuru Exchange: Market-WETH/USDC

3 conflicts on slot 0x3de775b20f…f1319b

← previous block·next block →recent activity