← previous blocknext block →recent activity
Analyzing
Block #87,296,187
24 transactions · 18 stateful · 2026-07-12 15:27:57 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,296,187 · 24 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
1w04w17w29w010w111w214w015w016w018w321w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x3ef0952c…762d
0x34b655…2a6f
4 touches
1 conflict
0x57f6fade…9347
0x34b655…2a6f
4 touches
1 conflict
0x57f6fade…9348
0x34b655…2a6f
4 touches
1 conflict
0x72880226…1435
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity