← previous blocknext block →recent activity
Analyzing
Block #86,977,179
14 transactions · 14 stateful · 2026-07-11 03:55:06 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,977,179 · 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
2w03w14w25w311w212w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05e76e1b…39ec
0x34b655…2a6f
10 touches
10 conflicts
0xb8c255af…052c
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd72f309e…fa65
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xb104db11…2208
0x34b655…2a6f
4 touches
1 conflict
0xce3de73c…ae35
0x34b655…2a6f
4 touches
1 conflict
0xce3de73c…ae36
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 0x05e76e1b2d…1839ec
Audit this contract →
← previous block·next block →recent activity