← previous blocknext block →recent activity
Analyzing
Block #106,428,533
32 transactions · 29 stateful · 2026-09-20 09:33:46 UTC
Parallelism
66/100
Blocked
66%
Avg conflicts / tx
2.38
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,428,533 · 32 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w26w213w322w424w625w726w727w828w829w930w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0262e1c6…52e1
0x34b655…2a6f
16 touches
28 conflicts
0x8f33447d…d0cd
0x34b655…2a6f
14 touches
21 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
10 touches
10 conflicts
0x4984f7be…d515
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xba33378a…f1df
0x34b655…2a6f
8 touches
6 conflicts
0xa45fa28d…9ded
0x34b655…2a6f
8 touches
6 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 0x0262e1c696…e752e1
Audit this contract →
← previous block·next block →recent activity