← previous blocknext block →recent activity
Analyzing
Block #87,352,022
11 transactions · 9 stateful · 2026-07-12 21:41:15 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,352,022 · 11 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
5w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xd6c45a31…9931
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0c487cde…b628
0x34b655…2a6f
2 touches
0 conflicts
0x2714ec54…3fb6
0x34b655…2a6f
2 touches
0 conflicts
0x819b5176…86cf
0x34b655…2a6f
2 touches
0 conflicts
0x9c87f480…4fbf
0x34b655…2a6f
2 touches
0 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity