← previous blocknext block →recent activity
Analyzing
Block #106,551,857
34 transactions · 34 stateful · 2026-09-20 19:54:30 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1.62
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,551,857 · 34 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
2w03w14w25w36w07w010w114w115w416w517w521w823w924w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fc536fb…1aa1
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x9733a5bf…f0fc
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
8 touches
6 conflicts
0x85277457…4ab9
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
21 conflicts on slot 0x0fc536fb1f…c81aa1
Audit this contract →
← previous block·next block →recent activity