← previous blocknext block →recent activity
Analyzing
Block #106,424,455
29 transactions · 26 stateful · 2026-09-20 09:13:15 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,424,455 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w19w010w111w212w313w415w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ede1c30…8bed
0x34b655…2a6f
10 touches
10 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
10 touches
10 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
10 touches
10 conflicts
0x4a45b318…9716
0x34b655…2a6f
10 touches
10 conflicts
0x5f76b8ee…ecfe
0x34b655…2a6f
10 touches
10 conflicts
0x74cdc294…26a8
0x34b655…2a6f
10 touches
10 conflicts
0x88fc2a68…3918
0x34b655…2a6f
10 touches
10 conflicts
0x9d6a99f9…da64
0x34b655…2a6f
10 touches
10 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
10 conflicts on slot 0x1ede1c30cd…008bed
Audit this contract →
← previous block·next block →recent activity