← previous blocknext block →recent activity
Analyzing
Block #87,419,956
15 transactions · 14 stateful · 2026-07-13 05:15:40 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,419,956 · 15 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
2w03w14w25w09w110w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x934da4f1…43a7
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x426e1f22…5ff9
0x34b655…2a6f
4 touches
1 conflict
0x458e55a6…fe6b
0x34b655…2a6f
4 touches
1 conflict
0x69028386…61a4
0x34b655…2a6f
4 touches
1 conflict
0x6c381064…bc43
0x34b655…2a6f
4 touches
1 conflict
0x87ee379a…cd9e
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 0x934da4f18d…ae43a7
Audit this contract →
← previous block·next block →recent activity