← previous blocknext block →recent activity
Analyzing
Block #106,199,198
24 transactions · 21 stateful · 2026-09-19 14:19:32 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,199,198 · 24 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
1w02w13w04w08w09w110w111w212w313w414w515w618w119w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5717771c…45ed
0x34b655…2a6f
10 touches
10 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x315e07b8…9823
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x63e42236…7963
0x34b655…2a6f
8 touches
6 conflicts
0x762445fc…df4d
0x34b655…2a6f
8 touches
6 conflicts
0x92b49f44…ee4f
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
10 conflicts on slot 0x5717771c41…8945ed
Audit this contract →
← previous block·next block →recent activity