← previous blocknext block →recent activity
Analyzing
Block #106,435,347
24 transactions · 23 stateful · 2026-09-20 10:08:05 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,435,347 · 24 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
2w03w14w05w06w19w211w016w218w319w420w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1927b58…f161
0x34b655…2a6f
12 touches
15 conflicts
0x4b4cd909…44a1
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0x8d175439…fb79
0x34b655…2a6f
6 touches
3 conflicts
0xac5f3ead…0195
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
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 0xb1927b5859…36f161
Audit this contract →
← previous block·next block →recent activity