← previous blocknext block →recent activity
Analyzing
Block #106,207,025
29 transactions · 26 stateful · 2026-09-19 14:58:59 UTC
Parallelism
69/100
Blocked
54%
Avg conflicts / tx
1.83
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,207,025 · 29 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
1w02w03w111w212w315w416w517w118w619w620w721w827w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79d68b83…d788
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
8 touches
6 conflicts
0x696abaea…eb3d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x35b89cd8…5092
0x34b655…2a6f
6 touches
3 conflicts
0xb0a4e112…f855
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 0x79d68b8351…b1d788
Audit this contract →
← previous block·next block →recent activity