← previous blocknext block →recent activity
Analyzing
Block #86,818,914
28 transactions · 17 stateful · 2026-07-10 10:17:04 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,818,914 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w011w112w215w216w019w325w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d888c90…5479
0x34b655…2a6f
8 touches
6 conflicts
0x772ab420…c2f6
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x489646ad…1521
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xf60062ab…f98c
0x34b655…2a6f
4 touches
1 conflict
0x00873542…6db6
0x34b655…2a6f
4 touches
1 conflict
0x2eac5688…c0eb
0x34b655…2a6f
4 touches
1 conflict
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 0x8d888c9003…aa5479
Audit this contract →
← previous block·next block →recent activity