← previous blocknext block →recent activity

Analyzing

Block #86,629,068

20 transactions · 17 stateful · 2026-07-09 13:07:51 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

0.7

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,629,068  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa08f40b2…9a93

0x34b655…2a6f

6 touches
3 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xa7013be2…c0a8

0x34b655…2a6f

4 touches
1 conflict

0xc9ba1c61…1c8e

0x34b655…2a6f

4 touches
1 conflict

0xd0cd3305…f212

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 0x0000000000…00003d

← previous block·next block →recent activity