← previous blocknext block →recent activity
Analyzing
Block #87,132,704
16 transactions · 15 stateful · 2026-07-11 21:14:02 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,132,704 · 16 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
4w05w16w27w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xf5c132ea…e166
0x34b655…2a6f
4 touches
1 conflict
0xdd38f4e6…586c
0x34b655…2a6f
4 touches
1 conflict
0xdd38f4e6…586d
0x34b655…2a6f
4 touches
1 conflict
0xeaed2cda…78bb
0x34b655…2a6f
4 touches
1 conflict
0xef5838dd…00a4
0x34b655…2a6f
4 touches
1 conflict
0x5ed58b36…c5e5
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity