← previous blocknext block →recent activity
Analyzing
Block #106,189,629
24 transactions · 23 stateful · 2026-09-19 13:31:23 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,189,629 · 24 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
1w02w03w14w25w36w07w18w19w215w416w217w118w521w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb654bd89…a83b
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x13c2d8a7…eb95
0x34b655…2a6f
8 touches
6 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
8 touches
6 conflicts
0x8ac18b8d…0c1c
0x34b655…2a6f
6 touches
3 conflicts
0x9340e06b…1581
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x365ac362…90c5
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 0xb654bd89ad…dba83b
Audit this contract →
← previous block·next block →recent activity