← previous blocknext block →recent activity
Analyzing
Block #86,980,809
20 transactions · 20 stateful · 2026-07-11 04:19:22 UTC
Parallelism
80/100
Blocked
15%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,980,809 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6c7e1952…d9c9
0x34b655…2a6f
6 touches
3 conflicts
0xe087db9c…7d87
0x34b655…2a6f
4 touches
1 conflict
0x0a6ba3b4…2123
0x34b655…2a6f
4 touches
1 conflict
0x4e782273…1690
0x34b655…2a6f
4 touches
1 conflict
0xdda45077…4cbb
0x40c49f…2af0
2 touches
0 conflicts
0xe2b3bf7e…566b
0x40c49f…2af0
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity