← previous blocknext block →recent activity
Analyzing
Block #105,672,443
26 transactions · 25 stateful · 2026-09-17 18:06:01 UTC
Parallelism
81/100
Blocked
16%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,672,443 · 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
2w06w17w29w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e9210b8…64ae
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x86bd79a5…1f48
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd99d25df…ecd8
0x34b655…2a6f
4 touches
1 conflict
0xf72228f6…970c
0x34b655…2a6f
4 touches
1 conflict
0x5a3c0271…4aed
0x34b655…2a6f
2 touches
0 conflicts
0x6c0e32fc…a6ca
0x34b655…2a6f
2 touches
0 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 0x0e9210b8b0…6c64ae
Audit this contract →
← previous block·next block →recent activity