← previous blocknext block →recent activity
Analyzing
Block #106,431,254
22 transactions · 21 stateful · 2026-09-20 09:47:28 UTC
Parallelism
55/100
Blocked
57%
Avg conflicts / tx
2.18
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,431,254 · 22 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
2w04w07w18w29w210w311w412w113w515w616w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2507c7b7…58f7
0x34b655…2a6f
18 touches
36 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x9a8482cc…8bee
0x34b655…2a6f
8 touches
6 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
8 touches
6 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x74e46435…fdcd
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
36 conflicts on slot 0x2507c7b76a…8058f7
Audit this contract →
← previous block·next block →recent activity