← previous blocknext block →recent activity
Analyzing
Block #106,923,803
28 transactions · 26 stateful · 2026-09-22 03:07:33 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,923,803 · 28 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
1w02w03w17w08w110w111w212w313w416w517w219w520w621w723w327w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf06565ba…77f7
0x34b655…2a6f
14 touches
21 conflicts
0x34c48330…703f
0x34b655…2a6f
12 touches
15 conflicts
0x574628e9…dcc3
0x34b655…2a6f
8 touches
6 conflicts
0xacd9c381…91d1
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x94e7f277…471b
0x34b655…2a6f
8 touches
6 conflicts
0xe4bcafbe…10fc
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
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 0xf06565ba57…5877f7
Audit this contract →
← previous block·next block →recent activity