← previous blocknext block →recent activity
Analyzing
Block #105,849,995
30 transactions · 30 stateful · 2026-09-18 09:01:02 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
3.03
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,849,995 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w112w113w214w215w316w417w518w619w420w521w722w823w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6caf33e2…c261
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
12 touches
15 conflicts
0x23529e13…6f25
0x34b655…2a6f
12 touches
15 conflicts
0xc10b903d…2f54
0x34b655…2a6f
10 touches
10 conflicts
0xa9cb3760…52d0
0x34b655…2a6f
8 touches
6 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 0x6caf33e26f…3dc261
Audit this contract →
← previous block·next block →recent activity