← previous blocknext block →recent activity
Analyzing
Block #86,980,034
12 transactions · 12 stateful · 2026-07-11 04:14:11 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,980,034 · 12 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
2w07w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x84849074…1ca2
0x34b655…2a6f
4 touches
1 conflict
0x42aad825…b067
0x34b655…2a6f
2 touches
0 conflicts
0x7a693a45…747c
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
2 touches
0 conflicts
0x87a24499…0acf
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity