← previous blocknext block →recent activity
Analyzing
Block #86,921,112
16 transactions · 15 stateful · 2026-07-10 21:40:30 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,921,112 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w211w112w313w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc57b566d…8591
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6bd6b33e…9557
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x3244bc68…5263
0x34b655…2a6f
4 touches
1 conflict
0x54200b1e…7ccd
0x34b655…2a6f
4 touches
1 conflict
0x7b0d2b3d…f176
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 0xc57b566d0e…eb8591
Audit this contract →
← previous block·next block →recent activity