← previous blocknext block →recent activity
Analyzing
Block #87,629,321
20 transactions · 17 stateful · 2026-07-14 04:36:35 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,629,321 · 20 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
2w03w15w26w07w111w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f8a50d…333b
0x34b655…2a6f
6 touches
3 conflicts
0x18904470…0ef9
0x34b655…2a6f
6 touches
3 conflicts
0xc2ee2f56…b6f5
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x4327afd2…1b3a
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a4
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 0x63f8a50db5…53333b
Audit this contract →
← previous block·next block →recent activity