← previous blocknext block →recent activity
Analyzing
Block #87,263,132
17 transactions · 17 stateful · 2026-07-12 11:46:56 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.59
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,263,132 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w38w410w511w612w716w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x0dd44476…ef40
0x34b655…2a6f
10 touches
10 conflicts
0x55c2c22c…0474
0x34b655…2a6f
10 touches
10 conflicts
0x263aa68b…6c6a
0x34b655…2a6f
6 touches
3 conflicts
0xf5042875…9a93
0x34b655…2a6f
6 touches
3 conflicts
0x819b5176…86cf
0x34b655…2a6f
4 touches
1 conflict
0x9816fc81…4f3d
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
21 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity