← previous blocknext block →recent activity
Analyzing
Block #106,216,658
21 transactions · 20 stateful · 2026-09-19 15:47:28 UTC
Parallelism
52/100
Blocked
65%
Avg conflicts / tx
2.14
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,216,658 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w18w29w210w311w414w515w616w717w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x163c8eca…7b49
0x34b655…2a6f
12 touches
15 conflicts
0xe6e64efa…fbce
0x34b655…2a6f
10 touches
10 conflicts
0xc685bf80…7ce6
0x34b655…2a6f
8 touches
6 conflicts
0x413451b2…b599
0x34b655…2a6f
6 touches
3 conflicts
0xfbabb02d…af07
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity