← previous blocknext block →recent activity
Analyzing
Block #106,281,764
26 transactions · 24 stateful · 2026-09-19 21:15:10 UTC
Parallelism
65/100
Blocked
54%
Avg conflicts / tx
2.08
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,281,764 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w29w311w313w414w516w618w519w620w721w825w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4634dcc…b675
0x34b655…2a6f
18 touches
36 conflicts
0x94e7f277…471b
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x885efce3…7496
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0x172b0de5…980b
0x34b655…2a6f
6 touches
3 conflicts
0x2c2db8e9…fdc7
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
36 conflicts on slot 0xb4634dccaa…4bb675
Audit this contract →
← previous block·next block →recent activity