← previous blocknext block →recent activity
Analyzing
Block #105,841,361
32 transactions · 30 stateful · 2026-09-18 08:17:26 UTC
Parallelism
50/100
Blocked
73%
Avg conflicts / tx
3.38
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #105,841,361 · 32 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w313w415w517w518w619w720w821w922w1023w1024w1125w1226w1327w1428w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72924751…cdcf
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x08731834…6415
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xb7ce83b1…2c96
0x34b655…2a6f
12 touches
15 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
10 touches
10 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 0x7292475160…45cdcf
Audit this contract →
← previous block·next block →recent activity