← previous blocknext block →recent activity
Analyzing
Block #106,575,618
21 transactions · 20 stateful · 2026-09-20 21:54:04 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,575,618 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w39w410w515w016w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33387c27…44cc
0x34b655…2a6f
12 touches
15 conflicts
0x110a3804…f842
0x34b655…2a6f
12 touches
15 conflicts
0xa6464996…3af9
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xa7b29d23…096f
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x922c733b…d7ec
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
15 conflicts on slot 0x33387c27c2…0644cc
Audit this contract →
← previous block·next block →recent activity