← previous blocknext block →recent activity

Analyzing

Block #86,083,772

18 transactions · 17 stateful · 2026-07-07 00:23:44 UTC

Parallelism

89/100

Blocked

29%

Avg conflicts / tx

0.39

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,083,772  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xbcdee322…f454

0xa6afd3…d132

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x1aaf4996…65ec

0x34b655…2a6f

4 touches
1 conflict

0x39cc2185…caca

0x34b655…2a6f

4 touches
1 conflict

0x6303c255…0b0c

0x34b655…2a6f

4 touches
1 conflict

0x6e19c9a0…7d86

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x17c44db3…8888

0xa6afd3…d132

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

1 conflict on slot 0xbcdee3220a…7cf454

← previous block·next block →recent activity