← previous blocknext block →recent activity
Analyzing
Block #105,856,838
24 transactions · 22 stateful · 2026-09-18 09:35:29 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,856,838 · 24 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
1w03w04w010w112w113w015w216w317w318w419w020w121w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x203d3e2c…fa40
0x34b655…2a6f
8 touches
6 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0xb3aa2022…9e09
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x5627bc34…3395
0x34b655…2a6f
4 touches
1 conflict
0x6455c121…f808
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
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
6 conflicts on slot 0x203d3e2ce9…53fa40
Audit this contract →
← previous block·next block →recent activity