← previous blocknext block →recent activity
Analyzing
Block #86,330,924
18 transactions · 16 stateful · 2026-07-08 03:53:56 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,330,924 · 18 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
1w02w13w04w15w26w38w110w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87ee379a…cd9e
0x34b655…2a6f
6 touches
3 conflicts
0xe5a9274d…78d7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x86071ac3…1310
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x034f1f86…4e8d
0x34b655…2a6f
4 touches
1 conflict
0x27f0e3c6…f709
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0x87ee379aa1…d8cd9e
Audit this contract →
← previous block·next block →recent activity