← previous blocknext block →recent activity
Analyzing
Block #106,954,142
23 transactions · 22 stateful · 2026-09-22 05:40:15 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,954,142 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w06w17w28w19w111w213w314w415w217w319w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4a1ecf7…9e63
0x34b655…2a6f
10 touches
10 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xf971f10a…3c2c
0x34b655…2a6f
8 touches
6 conflicts
0xcb5668a5…8a56
0x065c9d…c394
8 touches
6 conflicts
0x967df1b1…e02e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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
10 conflicts on slot 0xa4a1ecf705…e59e63
Audit this contract →
← previous block·next block →recent activity