← previous blocknext block →recent activity
Analyzing
Block #86,853,824
16 transactions · 12 stateful · 2026-07-10 14:10:35 UTC
Parallelism
81/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,853,824 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x599f7bb6…8a05
0x34b655…2a6f
4 touches
1 conflict
0x5d863b2f…bd28
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x20375a54…6235
0x065c9d…c394
2 touches
0 conflicts
0x3a41d6c9…b83f
0x065c9d…c394
2 touches
0 conflicts
0x8ad01547…1938
0x065c9d…c394
2 touches
0 conflicts
0x8e7f3e47…e0ba
0x065c9d…c394
2 touches
0 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
1 conflict on slot 0x599f7bb626…7e8a05
Audit this contract →
← previous block·next block →recent activity