← previous blocknext block →recent activity
Analyzing
Block #106,546,442
30 transactions · 27 stateful · 2026-09-20 19:27:14 UTC
Parallelism
50/100
Blocked
63%
Avg conflicts / tx
2.7
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,546,442 · 30 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w36w111w214w415w518w619w720w821w922w1023w1124w1225w1326w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x735a86cd…b64d
0x34b655…2a6f
24 touches
66 conflicts
0x858f48fa…3413
0x34b655…2a6f
12 touches
15 conflicts
0xa6cbc1a2…9f44
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x92669466…3296
0x34b655…2a6f
8 touches
6 conflicts
0xf788c790…e66f
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x3b6e959d…158f
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
66 conflicts on slot 0x735a86cd19…53b64d
Audit this contract →
← previous block·next block →recent activity