← previous blocknext block →recent activity
Analyzing
Block #106,419,769
23 transactions · 21 stateful · 2026-09-20 08:49:40 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,419,769 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w28w313w315w116w417w518w621w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22fc5161…e258
0x34b655…2a6f
12 touches
15 conflicts
0x5e1c23e9…4f81
0x34b655…2a6f
8 touches
6 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
8 touches
6 conflicts
0xdbd130fe…a03c
0x34b655…2a6f
6 touches
3 conflicts
0x8c6f8a15…2930
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
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 0x22fc516177…b0e258
Audit this contract →
← previous block·next block →recent activity