← previous blocknext block →recent activity
Analyzing
Block #86,658,090
31 transactions · 20 stateful · 2026-07-09 16:23:06 UTC
Parallelism
84/100
Blocked
30%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,658,090 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w19w010w113w014w215w228w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bf5914f…c75d
0x34b655…2a6f
8 touches
6 conflicts
0x681dd2e1…ce40
0x34b655…2a6f
6 touches
3 conflicts
0xaeb149f0…a92e
0x34b655…2a6f
6 touches
3 conflicts
0x648ccbb2…2aa2
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x7b3da897…b268
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x2bf5914fac…c4c75d
Audit this contract →
← previous block·next block →recent activity