← previous blocknext block →recent activity
Analyzing
Block #87,504,421
16 transactions · 12 stateful · 2026-07-13 14:40:30 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,504,421 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w09w210w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44e13e21…432d
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x17c70f19…23a7
0x34b655…2a6f
4 touches
1 conflict
0x63973089…1c5c
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x64aed863…94cd
0x34b655…2a6f
4 touches
1 conflict
0x6aa7a02c…cbe9
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 0x44e13e2103…5d432d
Audit this contract →
← previous block·next block →recent activity