← previous blocknext block →recent activity
Analyzing
Block #105,853,158
28 transactions · 27 stateful · 2026-09-18 09:16:57 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,853,158 · 28 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
1w02w13w24w25w09w315w016w018w320w121w222w323w426w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7b20cb4…a869
0x34b655…2a6f
10 touches
10 conflicts
0xdc9915b5…542c
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd79c9727…1233
0x34b655…2a6f
8 touches
6 conflicts
0x045532dd…4b7d
0x34b655…2a6f
8 touches
6 conflicts
0xba5743c7…21c6
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x51fc8795…126f
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
10 conflicts on slot 0xe7b20cb46d…58a869
Audit this contract →
← previous block·next block →recent activity