← previous blocknext block →recent activity
Analyzing
Block #87,065,088
17 transactions · 17 stateful · 2026-07-11 13:42:28 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,065,088 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w313w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801058a8…5bc3
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa7e2f1b7…7e6f
0x34b655…2a6f
6 touches
3 conflicts
0x3083951a…4fa0
0x34b655…2a6f
6 touches
3 conflicts
0xe57232b3…0fbf
0x34b655…2a6f
6 touches
3 conflicts
0x00bbd28c…e227
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
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 0x801058a816…5a5bc3
Audit this contract →
← previous block·next block →recent activity