← previous blocknext block →recent activity
Analyzing
Block #86,757,915
21 transactions · 18 stateful · 2026-07-10 03:29:43 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,757,915 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w09w110w211w312w313w215w416w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x61631446…70ac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc8f6f7a3…f563
0x34b655…2a6f
6 touches
3 conflicts
0xc8f6f7a3…f564
0x34b655…2a6f
6 touches
3 conflicts
0xeeb46b9e…93e1
0x34b655…2a6f
6 touches
3 conflicts
0xf3e03381…8f72
0x34b655…2a6f
6 touches
3 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
6 touches
3 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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity