← previous blocknext block →recent activity
Analyzing
Block #106,932,811
22 transactions · 21 stateful · 2026-09-22 03:52:53 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,932,811 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w49w110w211w512w613w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4786839b…c29a
0x34b655…2a6f
12 touches
15 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x79dcc7d9…caaa
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0x9a339ea4…3cd6
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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 0x4786839b71…e2c29a
Audit this contract →
← previous block·next block →recent activity