← previous blocknext block →recent activity
Analyzing
Block #106,381,421
22 transactions · 21 stateful · 2026-09-20 05:36:41 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,381,421 · 22 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
1w02w13w14w011w213w014w115w216w317w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x001c2075…94d9
0x6f6493…b480
8 touches
6 conflicts
0x11c35e63…4296
0x6f6493…b480
8 touches
6 conflicts
0x14665f71…7c14
0x6f6493…b480
8 touches
6 conflicts
0x147775a5…0087
0x6f6493…b480
8 touches
6 conflicts
0x29e0a4a1…f438
0x6f6493…b480
8 touches
6 conflicts
0x372557ab…e2d3
0x6f6493…b480
8 touches
6 conflicts
0x3bd2f4ce…5d29
0x6f6493…b480
8 touches
6 conflicts
0x3f0e8df2…fa3f
0x6f6493…b480
8 touches
6 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: 0x6f6493e3…08b480
6 conflicts on slot 0x001c20754d…f794d9
Audit this contract →
← previous block·next block →recent activity