← previous blocknext block →recent activity
Analyzing
Block #106,420,884
21 transactions · 15 stateful · 2026-09-20 08:55:16 UTC
Parallelism
62/100
Blocked
60%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,420,884 · 21 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
1w05w06w18w210w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbe9d1d23…3de2
0x34b655…2a6f
12 touches
15 conflicts
0x5b1df4f9…0e64
0x34b655…2a6f
10 touches
10 conflicts
0xf89f5e80…5215
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7cd9fd28…a158
0x34b655…2a6f
6 touches
3 conflicts
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0x3ca268be…8865
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity