← previous blocknext block →recent activity
Analyzing
Block #106,199,710
26 transactions · 24 stateful · 2026-09-19 14:22:07 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.92
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,199,710 · 26 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
3w06w112w213w317w418w519w621w722w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa055b5a…1517
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0x7cf3eb0f…06c5
0x34b655…2a6f
6 touches
3 conflicts
0x75978698…0751
0x34b655…2a6f
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
6 touches
3 conflicts
0x581b829b…9578
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 0xaa055b5a5c…181517
Audit this contract →
← previous block·next block →recent activity