← previous blocknext block →recent activity

Analyzing

Block #87,876,197

23 transactions · 14 stateful · 2026-07-15 08:07:52 UTC

Parallelism

87/100

Blocked

57%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,876,197  ·  23 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x067c61b8…650f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x9f83113a…dcd8

0x34b655…2a6f

6 touches
3 conflicts

0x3e0ef032…8627

0x34b655…2a6f

4 touches
1 conflict

0x4ab0fef9…caef

0x34b655…2a6f

4 touches
1 conflict

0x517d8281…14d1

0x34b655…2a6f

4 touches
1 conflict

0x517d8281…14d2

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

3 conflicts on slot 0x067c61b803…d7650f

← previous block·next block →recent activity