← previous blocknext block →recent activity
Analyzing
Block #86,962,358
32 transactions · 26 stateful · 2026-07-11 02:16:07 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,962,358 · 32 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
2w03w04w113w014w116w017w118w219w020w121w223w124w329w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xd9f1e40f…09a3
0x3bd359…433a
6 touches
3 conflicts
0x527f20e3…82e7
0x754704…b603
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x28c180e1…f1e2
0x34b655…2a6f
6 touches
3 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
6 touches
3 conflicts
0xfcaee83d…428d
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity