← previous blocknext block →recent activity
Analyzing
Block #106,555,995
26 transactions · 24 stateful · 2026-09-20 20:15:19 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,555,995 · 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
1w06w08w110w011w114w115w216w317w418w519w620w724w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x646dd8ae…60c5
0x34b655…2a6f
14 touches
21 conflicts
0xb654bd89…a83b
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7462b8f2…6312
0x34b655…2a6f
8 touches
6 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
6 touches
3 conflicts
0x810a3aa2…0227
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
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 0x646dd8aedf…a960c5
Audit this contract →
← previous block·next block →recent activity