← previous blocknext block →recent activity
Analyzing
Block #105,461,535
23 transactions · 21 stateful · 2026-09-17 00:24:28 UTC
Parallelism
65/100
Blocked
48%
Avg conflicts / tx
1.09
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,461,535 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w17w213w214w315w416w517w618w721w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x178a61ad…4958
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xf496f80c…d5c8
0x34b655…2a6f
8 touches
6 conflicts
0x5d00cdd2…3e13
0x34b655…2a6f
6 touches
3 conflicts
0x13d4d00c…f4e6
0x34b655…2a6f
6 touches
3 conflicts
0x5bfc49d6…bd89
0x34b655…2a6f
6 touches
3 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0x178a61ad8a…8c4958
Audit this contract →
← previous block·next block →recent activity