← previous blocknext block →recent activity
Analyzing
Block #86,955,907
10 transactions · 9 stateful · 2026-07-11 01:32:59 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,955,907 · 10 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
3w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf96f1cdc…d66e
0x34b655…2a6f
6 touches
3 conflicts
0x35d95fb0…db9f
0x34b655…2a6f
4 touches
1 conflict
0xebeee24a…ed8d
0x34b655…2a6f
4 touches
1 conflict
0xf29e5320…ce2d
0x34b655…2a6f
4 touches
1 conflict
0x35d95fb0…db9e
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
2 touches
0 conflicts
0x3f5c5d31…c3c2
0x34b655…2a6f
2 touches
0 conflicts
0x78984ebe…9e90
0x34b655…2a6f
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
3 conflicts on slot 0xf96f1cdc98…1dd66e
Audit this contract →
← previous block·next block →recent activity