← previous blocknext block →recent activity
Analyzing
Block #86,772,709
14 transactions · 12 stateful · 2026-07-10 05:08:32 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,772,709 · 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
1w06w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78f9dd3b…66e1
0x34b655…2a6f
4 touches
1 conflict
0xf6971361…0e3e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x6e90b9b1…dca8
0x34b655…2a6f
4 touches
1 conflict
0x72011921…8ad4
0xd32edf…ff58
3 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x78f9dd3bc3…8266e1
Audit this contract →
← previous block·next block →recent activity