← previous blocknext block →recent activity
Analyzing
Block #106,408,444
33 transactions · 28 stateful · 2026-09-20 07:52:40 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
1.18
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,408,444 · 33 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w69w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1927b58…f161
0x34b655…2a6f
16 touches
28 conflicts
0x4118bd12…924a
0x34b655…2a6f
8 touches
6 conflicts
0xc1a963ef…c582
0x34b655…2a6f
8 touches
6 conflicts
0xb8b56c37…9859
0x34b655…2a6f
8 touches
6 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
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
28 conflicts on slot 0xb1927b5859…36f161
Audit this contract →
← previous block·next block →recent activity