← previous blocknext block →recent activity
Analyzing
Block #106,930,655
25 transactions · 24 stateful · 2026-09-22 03:42:02 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,930,655 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w210w312w213w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70986451…c6bd
0x34b655…2a6f
12 touches
15 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
10 touches
10 conflicts
0x251ee419…4404
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x98783aa8…b36c
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x85c5ea16…1194
0x34b655…2a6f
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
15 conflicts on slot 0x7098645134…3ac6bd
Audit this contract →
← previous block·next block →recent activity