← previous blocknext block →recent activity
Analyzing
Block #106,217,011
19 transactions · 19 stateful · 2026-09-19 15:49:15 UTC
Parallelism
84/100
Blocked
26%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,217,011 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w012w113w114w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b6af007…0f35
0x34b655…2a6f
6 touches
3 conflicts
0x1d1f4fb6…320b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xff675495…5381
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x8fe3a63b…7f21
0x34b655…2a6f
4 touches
1 conflict
0x5e2ea201…12de
0x34b655…2a6f
4 touches
1 conflict
0xc389d1ff…6a00
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x5b6af0070f…160f35
Audit this contract →
← previous block·next block →recent activity