← previous blocknext block →recent activity
Analyzing
Block #106,234,806
30 transactions · 30 stateful · 2026-09-19 17:18:51 UTC
Parallelism
70/100
Blocked
73%
Avg conflicts / tx
1.87
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,234,806 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w26w37w412w513w514w615w716w6
- 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
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x44308ada…595d
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x7deb183c…0858
0x34b655…2a6f
8 touches
6 conflicts
0x4d1ba25f…6eb2
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