← previous blocknext block →recent activity
Analyzing
Block #105,851,121
17 transactions · 16 stateful · 2026-09-18 09:06:42 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,851,121 · 17 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
3w05w111w012w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6caf33e2…c261
0x34b655…2a6f
10 touches
10 conflicts
0xc7b7b345…1d04
0x34b655…2a6f
10 touches
10 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
10 touches
10 conflicts
0x932a9590…0b19
0x34b655…2a6f
8 touches
6 conflicts
0xc263101a…911c
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x1afd1723…2a45
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
10 conflicts on slot 0x6caf33e26f…3dc261
Audit this contract →
← previous block·next block →recent activity