← previous blocknext block →recent activity
Analyzing
Block #106,408,289
22 transactions · 21 stateful · 2026-09-20 07:51:53 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,408,289 · 22 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
1w02w03w16w18w210w311w412w114w415w318w519w620w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x760fc6c3…71f9
0x34b655…2a6f
14 touches
21 conflicts
0x310a7246…2dcb
0x34b655…2a6f
10 touches
10 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
10 touches
10 conflicts
0xb9b077a8…e029
0x34b655…2a6f
8 touches
6 conflicts
0xef948c34…0463
0x34b655…2a6f
8 touches
6 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
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
21 conflicts on slot 0x760fc6c389…7b71f9
Audit this contract →
← previous block·next block →recent activity