← previous blocknext block →recent activity
Analyzing
Block #101,088,054
23 transactions · 18 stateful · 2026-09-01 16:19:36 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,088,054 · 23 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
1w04w18w09w110w211w012w116w017w018w219w320w322w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0235b23…d13d
0x34b655…2a6f
6 touches
3 conflicts
0x1e168c8b…6945
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xbd590df7…9891
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
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
3 conflicts on slot 0xf0235b230f…35d13d
Audit this contract →
← previous block·next block →recent activity