← previous blocknext block →recent activity
Analyzing
Block #86,693,159
14 transactions · 12 stateful · 2026-07-09 20:17:05 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,693,159 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w08w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2adb2e5d…fea3
0x34b655…2a6f
4 touches
1 conflict
0x1c03f81f…b303
0x34b655…2a6f
4 touches
1 conflict
0x7ce93f3d…b70e
0x34b655…2a6f
4 touches
1 conflict
0x1c03f81f…b304
0x34b655…2a6f
4 touches
1 conflict
0xb4fdc4a4…5b2e
0x34b655…2a6f
4 touches
1 conflict
0x058fe5e8…23dc
0x34b655…2a6f
3 touches
1 conflict
0x5bb46f6c…7693
0x34b655…2a6f
2 touches
0 conflicts
0xa5ab7b8a…c97b
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
1 conflict on slot 0x2adb2e5df4…e0fea3
Audit this contract →
← previous block·next block →recent activity