← previous blocknext block →recent activity
Analyzing
Block #106,537,667
25 transactions · 24 stateful · 2026-09-20 18:43:05 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,537,667 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w26w016w018w119w120w221w322w423w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb807cc04…4606
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xe098738f…9bbe
0x34b655…2a6f
8 touches
6 conflicts
0x549c41f3…3e6c
0x34b655…2a6f
8 touches
6 conflicts
0x69411fb3…e36d
0x34b655…2a6f
8 touches
6 conflicts
0x9a6d78b0…b736
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
10 conflicts on slot 0xb807cc0413…784606
Audit this contract →
← previous block·next block →recent activity