← previous blocknext block →recent activity

Analyzing

Block #87,722,965

26 transactions · 20 stateful · 2026-07-14 15:02:54 UTC

Parallelism

81/100

Blocked

45%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,722,965  ·  26 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

0xd9f1e40f…09a3

0x3bd359…433a

8 touches
6 conflicts

0x527f20e3…82e7

0x754704…b603

8 touches
6 conflicts

0x4cee015b…1a5e

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

6 touches
3 conflicts

0x0dd44476…ef40

0x34b655…2a6f

6 touches
3 conflicts

0x43cea534…ddce

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5a7505f7…a94d

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: Wrapped MON (WMON)

6 conflicts on slot 0xd9f1e40f03…3209a3

← previous block·next block →recent activity