← previous blocknext block →recent activity
Analyzing
Block #86,619,902
22 transactions · 19 stateful · 2026-07-09 12:06:41 UTC
Parallelism
77/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,619,902 · 22 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
4w05w16w27w110w211w312w414w015w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b5d2e60…99b5
0x34b655…2a6f
6 touches
3 conflicts
0x4caf91f9…8ab5
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0xb2fa7755…4c09
0x34b655…2a6f
6 touches
3 conflicts
0xe5d48e35…6b67
0x34b655…2a6f
6 touches
3 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
6 touches
3 conflicts
0x90e113f8…c8f9
0xc8689a…ee79
6 touches
3 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
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 0x1b5d2e607a…9999b5
Audit this contract →
← previous block·next block →recent activity