← previous blocknext block →recent activity
Analyzing
Block #106,217,000
23 transactions · 20 stateful · 2026-09-19 15:49:11 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.52
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,217,000 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf99856c4…370d
0x34b655…2a6f
16 touches
28 conflicts
0x5b6af007…0f35
0x34b655…2a6f
10 touches
10 conflicts
0x5e2ea201…12de
0x34b655…2a6f
10 touches
10 conflicts
0x1b3df55c…8693
0x34b655…2a6f
8 touches
6 conflicts
0x1bfbc645…588e
0x34b655…2a6f
8 touches
6 conflicts
0x4333a7b3…a221
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x69206649…3b2a
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 0xf99856c491…9a370d
Audit this contract →
← previous block·next block →recent activity