← previous blocknext block →recent activity
Analyzing
Block #86,250,609
26 transactions · 23 stateful · 2026-07-07 18:57:44 UTC
Parallelism
81/100
Blocked
26%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,250,609 · 26 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
1w02w13w25w38w418w019w020w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6af306bb…2e81
0x3bd359…433a
6 touches
3 conflicts
0xf91b744e…9117
0x754704…b603
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
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: Wrapped MON (WMON)
3 conflicts on slot 0x6af306bb1d…092e81
Audit this contract →
← previous block·next block →recent activity