← previous blocknext block →recent activity
Analyzing
Block #87,064,783
17 transactions · 16 stateful · 2026-07-11 13:40:26 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,064,783 · 17 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
1w03w14w05w16w27w38w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x021dd282…c5ef
0x34b655…2a6f
4 touches
1 conflict
0x086db8fc…0024
0x34b655…2a6f
4 touches
1 conflict
0x0c69433a…4f81
0x34b655…2a6f
4 touches
1 conflict
0x15072088…a605
0x34b655…2a6f
4 touches
1 conflict
0x1db0096b…d655
0x34b655…2a6f
4 touches
1 conflict
0x1ef08681…1026
0x34b655…2a6f
4 touches
1 conflict
0x226feee2…63ef
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity