← previous blocknext block →recent activity
Analyzing
Block #87,588,701
21 transactions · 19 stateful · 2026-07-14 00:04:55 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,588,701 · 21 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
2w03w14w25w39w010w111w413w318w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xe6bc2816…1787
0x34b655…2a6f
6 touches
3 conflicts
0x18904470…0ef9
0x34b655…2a6f
4 touches
1 conflict
0x18ffdaac…23bd
0x34b655…2a6f
4 touches
1 conflict
0x1d276529…2b8c
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x63f8a50d…333b
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity