← previous blocknext block →recent activity
Analyzing
Block #106,772,280
20 transactions · 19 stateful · 2026-09-21 14:24:49 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,772,280 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w19w010w112w014w115w216w317w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x14059da3…4191
0x6f6493…b480
4 touches
1 conflict
0x17574d14…7754
0x6f6493…b480
4 touches
1 conflict
0x203995bb…52a3
0x6f6493…b480
4 touches
1 conflict
0x2bfcf939…767d
0x6f6493…b480
4 touches
1 conflict
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity