← previous blocknext block →recent activity
Analyzing
Block #86,987,296
17 transactions · 16 stateful · 2026-07-11 05:02:42 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,987,296 · 17 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
4w05w16w27w39w211w312w313w416w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x6a6e42c5…9438
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x26918bca…6c75
0x34b655…2a6f
4 touches
1 conflict
0x276ed918…4bb5
0x34b655…2a6f
4 touches
1 conflict
0x2f23558a…8e0b
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity