← previous blocknext block →recent activity
Analyzing
Block #105,672,778
23 transactions · 21 stateful · 2026-09-17 18:07:43 UTC
Parallelism
74/100
Blocked
33%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,672,778 · 23 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
1w03w04w114w117w218w319w421w222w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3b620ed…64f4
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x43e3decb…be40
0x34b655…2a6f
8 touches
6 conflicts
0x70f537e8…399b
0x34b655…2a6f
8 touches
6 conflicts
0xb5f5f775…010b
0x34b655…2a6f
6 touches
3 conflicts
0xdaf02dea…dbd8
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x706c758c…2fdb
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
10 conflicts on slot 0xb3b620ede1…4864f4
Audit this contract →
← previous block·next block →recent activity