← previous blocknext block →recent activity
Analyzing
Block #105,929,331
25 transactions · 24 stateful · 2026-09-18 15:41:13 UTC
Parallelism
68/100
Blocked
46%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,929,331 · 25 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
1w02w13w04w17w28w213w314w415w418w519w620w724w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe705b8ed…a096
0x34b655…2a6f
14 touches
21 conflicts
0xdb11940a…519b
0x34b655…2a6f
8 touches
6 conflicts
0x581a35d8…d303
0x34b655…2a6f
8 touches
6 conflicts
0x932a9590…0b19
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1afd1723…2a45
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
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
21 conflicts on slot 0xe705b8edf6…27a096
Audit this contract →
← previous block·next block →recent activity