← previous blocknext block →recent activity
Analyzing
Block #106,916,965
26 transactions · 24 stateful · 2026-09-22 02:33:07 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
1.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,916,965 · 26 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
1w04w05w17w18w29w310w420w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb002bdaf…5627
0x34b655…2a6f
14 touches
21 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
12 touches
15 conflicts
0xf7b76d2f…1b9c
0x34b655…2a6f
8 touches
6 conflicts
0x07bc7a81…f78a
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0x69411fb3…e36d
0x34b655…2a6f
8 touches
6 conflicts
0x834f2fbe…e576
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xb002bdafb3…735627
Audit this contract →
← previous block·next block →recent activity