← previous blocknext block →recent activity
Analyzing
Block #106,385,591
22 transactions · 20 stateful · 2026-09-20 05:57:40 UTC
Parallelism
55/100
Blocked
65%
Avg conflicts / tx
2.09
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,385,591 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w16w07w18w210w311w313w414w515w617w718w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e665745…8517
0x34b655…2a6f
18 touches
36 conflicts
0x8d175439…fb79
0x34b655…2a6f
10 touches
10 conflicts
0x51d607f1…6458
0x34b655…2a6f
8 touches
6 conflicts
0xba9f9225…2ead
0x34b655…2a6f
8 touches
6 conflicts
0xba33378a…f1df
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xda6b535e…6d69
0x1b6862…e19c
6 touches
3 conflicts
0x0490581d…adaf
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
36 conflicts on slot 0x1e66574536…6d8517
Audit this contract →
← previous block·next block →recent activity