← previous blocknext block →recent activity
Analyzing
Block #87,524,538
23 transactions · 20 stateful · 2026-07-13 16:55:38 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,524,538 · 23 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
2w03w15w06w07w18w29w311w012w413w514w216w621w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3688185…9b36
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xa86351b8…2c5a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x85ac0ab8…a3d8
0x34b655…2a6f
6 touches
3 conflicts
0xced3c179…c885
0x34b655…2a6f
4 touches
1 conflict
0xd2888385…2e9a
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 0xc36881859a…c49b36
Audit this contract →
← previous block·next block →recent activity