← previous blocknext block →recent activity
Analyzing
Block #106,468,183
22 transactions · 22 stateful · 2026-09-20 12:53:23 UTC
Parallelism
64/100
Blocked
59%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,468,183 · 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
1w02w13w24w05w16w27w110w211w312w413w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d664414…3344
0x34b655…2a6f
14 touches
21 conflicts
0x17953a45…96a1
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x5f1ffb67…59a2
0x34b655…2a6f
10 touches
10 conflicts
0x30ae635d…5e67
0x34b655…2a6f
8 touches
6 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x043c6dd5…b6e3
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 0x8d664414de…103344
Audit this contract →
← previous block·next block →recent activity