← previous blocknext block →recent activity
Analyzing
Block #86,789,153
12 transactions · 11 stateful · 2026-07-10 06:58:14 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,789,153 · 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
5w06w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb8f817d7…8e60
0x34b655…2a6f
4 touches
1 conflict
0xc2775c92…702a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x167de262…f61f
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0x6d99ac64…0aa3
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity