← previous blocknext block →recent activity
Analyzing
Block #106,224,476
23 transactions · 21 stateful · 2026-09-19 16:26:49 UTC
Parallelism
65/100
Blocked
48%
Avg conflicts / tx
1.57
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,224,476 · 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
2w03w14w08w212w214w315w117w418w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2d5c309…882d
0x34b655…2a6f
14 touches
21 conflicts
0xbf0dd721…6823
0x34b655…2a6f
14 touches
21 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5b6af007…0f35
0x34b655…2a6f
8 touches
6 conflicts
0xc737ce4f…a8d8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x24ed74ea…a3ff
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 0xd2d5c309fb…7a882d
Audit this contract →
← previous block·next block →recent activity