← previous blocknext block →recent activity
Analyzing
Block #106,190,874
23 transactions · 21 stateful · 2026-09-19 13:37:39 UTC
Parallelism
65/100
Blocked
52%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,190,874 · 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
1w02w13w04w16w07w08w111w212w313w414w415w516w617w722w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51f1f20c…d9da
0x34b655…2a6f
12 touches
15 conflicts
0xbb2316a2…23cd
0x34b655…2a6f
10 touches
10 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
10 touches
10 conflicts
0x315e07b8…9823
0x34b655…2a6f
8 touches
6 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
8 touches
6 conflicts
0xfefb0189…f726
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
15 conflicts on slot 0x51f1f20c1e…7ad9da
Audit this contract →
← previous block·next block →recent activity