← previous blocknext block →recent activity
Analyzing
Block #106,189,077
20 transactions · 19 stateful · 2026-09-19 13:28:37 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,189,077 · 20 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
1w02w13w24w38w110w111w012w213w314w115w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd41f5136…97c6
0x34b655…2a6f
12 touches
15 conflicts
0x422880a0…e715
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xf58eca50…59fc
0x1b6862…e19c
8 touches
6 conflicts
0x1a29c64d…e772
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
15 conflicts on slot 0xd41f513688…4197c6
Audit this contract →
← previous block·next block →recent activity