← previous blocknext block →recent activity
Analyzing
Block #86,933,180
27 transactions · 17 stateful · 2026-07-10 23:01:10 UTC
Parallelism
93/100
Blocked
18%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,933,180 · 27 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
6w07w08w19w119w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ba014e3…35d5
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x94e0f6b9…3c85
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641c
0x34b655…2a6f
2 touches
0 conflicts
0xfde01750…f190
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 0x3ba014e38a…cf35d5
Audit this contract →
← previous block·next block →recent activity