← previous blocknext block →recent activity
Analyzing
Block #87,057,114
17 transactions · 17 stateful · 2026-07-11 12:49:17 UTC
Parallelism
41/100
Blocked
53%
Avg conflicts / tx
2.29
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,057,114 · 17 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w49w513w614w716w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
18 touches
36 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x1dddd7ef…8f05
0x34b655…2a6f
10 touches
10 conflicts
0x676d5418…85ea
0x34b655…2a6f
8 touches
6 conflicts
0x74fce6ad…7895
0x34b655…2a6f
8 touches
6 conflicts
0x8ae7d283…20b7
0x34b655…2a6f
8 touches
6 conflicts
0xcdd95ca7…a9c8
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity