← previous blocknext block →recent activity
Analyzing
Block #106,198,631
22 transactions · 20 stateful · 2026-09-19 14:16:41 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,198,631 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w28w311w413w014w115w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a9e408e…3721
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x366a19b0…f065
0x34b655…2a6f
6 touches
3 conflicts
0x68292fe7…d918
0x34b655…2a6f
6 touches
3 conflicts
0xa3ff1ab2…8ae3
0x34b655…2a6f
6 touches
3 conflicts
0xb644bb2e…e85b
0x34b655…2a6f
6 touches
3 conflicts
0xc97709e8…0f3a
0x34b655…2a6f
6 touches
3 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
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
6 conflicts on slot 0x6a9e408e97…fb3721
Audit this contract →
← previous block·next block →recent activity