← previous blocknext block →recent activity
Analyzing
Block #86,844,476
20 transactions · 18 stateful · 2026-07-10 13:08:08 UTC
Parallelism
55/100
Blocked
44%
Avg conflicts / tx
1.25
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,844,476 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w39w410w511w617w718w8
- 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
12 touches
15 conflicts
0xec7fe04a…3c56
0x34b655…2a6f
8 touches
6 conflicts
0x6ba89834…1826
0x34b655…2a6f
6 touches
3 conflicts
0xd987e2a5…484b
0x34b655…2a6f
6 touches
3 conflicts
0x010d4ce0…8cf0
0x34b655…2a6f
6 touches
3 conflicts
0xd7e486fa…8759
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
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