← previous blocknext block →recent activity

Analyzing

Block #87,909,898

20 transactions · 18 stateful · 2026-07-15 11:53:18 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,909,898  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc36fa358…24cb

0x34b655…2a6f

8 touches
6 conflicts

0xab96ac84…a512

0x34b655…2a6f

6 touches
3 conflicts

0xf28cf8dc…b0ca

0x34b655…2a6f

6 touches
3 conflicts

0x59bfb0ed…ebd2

0x34b655…2a6f

6 touches
3 conflicts

0x33da0dfa…bac6

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x4426bf1e…532a

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: Perpl

6 conflicts on slot 0xc36fa35805…6f24cb

← previous block·next block →recent activity