← previous blocknext block →recent activity
Analyzing
Block #106,916,244
34 transactions · 33 stateful · 2026-09-22 02:29:30 UTC
Parallelism
62/100
Blocked
58%
Avg conflicts / tx
1.35
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,916,244 · 34 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w08w19w212w013w115w216w317w418w519w621w724w826w927w131w1032w1133w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4af4c87…9964
0x34b655…2a6f
14 touches
21 conflicts
0x17d75238…7d7c
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x574628e9…dcc3
0x34b655…2a6f
8 touches
6 conflicts
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x08f9abf1…10bf
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 0xe4af4c87c3…c59964
Audit this contract →
← previous block·next block →recent activity