← previous blocknext block →recent activity
Analyzing
Block #87,121,376
10 transactions · 9 stateful · 2026-07-11 19:58:23 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,121,376 · 10 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52d2a422…f1ea
0x34b655…2a6f
4 touches
1 conflict
0xe4b8f2c5…f54d
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xfebaf6fc…61b5
0x34b655…2a6f
4 touches
1 conflict
0x4c7b72e8…9a1f
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7634a3f4…7f24
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 0x52d2a4227f…8df1ea
Audit this contract →
← previous block·next block →recent activity