← previous blocknext block →recent activity
Analyzing
Block #86,784,336
19 transactions · 17 stateful · 2026-07-10 06:26:04 UTC
Parallelism
74/100
Blocked
29%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,784,336 · 19 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
5w09w110w115w216w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
6 touches
3 conflicts
0x50887223…db7f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe9452241…95a3
0x34b655…2a6f
6 touches
3 conflicts
0x1a5d321d…a474
0x34b655…2a6f
6 touches
3 conflicts
0x4dd3fcaa…e1e2
0x34b655…2a6f
4 touches
1 conflict
0x5ddf1cf9…a8ba
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity