← previous blocknext block →recent activity
Analyzing
Block #87,583,749
14 transactions · 13 stateful · 2026-07-13 23:31:49 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,583,749 · 14 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
3w07w18w09w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde980d9c…7f68
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xf83b23f9…5a2f
0x34b655…2a6f
6 touches
3 conflicts
0xf6971361…0e3e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x0fedf54f…57fc
0x34b655…2a6f
4 touches
1 conflict
0x36187d32…57e2
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
6 conflicts on slot 0xde980d9c4d…517f68
Audit this contract →
← previous block·next block →recent activity