← previous blocknext block →recent activity
Analyzing
Block #87,052,292
14 transactions · 14 stateful · 2026-07-11 12:17:00 UTC
Parallelism
79/100
Blocked
14%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,052,292 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85c84f98…06d7
0x34b655…2a6f
4 touches
1 conflict
0x9199a85a…acd9
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x48e6f054…d2ac
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0xb6e4c137…bfe3
0x40c49f…2af0
2 touches
0 conflicts
0xfeb42fc4…1a13
0x40c49f…2af0
2 touches
0 conflicts
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
1 conflict on slot 0x85c84f9817…2806d7
Audit this contract →
← previous block·next block →recent activity