← previous blocknext block →recent activity
Analyzing
Block #106,538,132
24 transactions · 23 stateful · 2026-09-20 18:45:25 UTC
Parallelism
75/100
Blocked
57%
Avg conflicts / tx
1.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,538,132 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w28w39w415w319w420w521w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb53e864d…e48d
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
10 touches
10 conflicts
0xe098738f…9bbe
0x34b655…2a6f
10 touches
10 conflicts
0xaa3b4402…74e6
0x34b655…2a6f
10 touches
10 conflicts
0xae8cf41a…ddb6
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x46a5ec6c…f318
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
15 conflicts on slot 0xb53e864d5f…f3e48d
Audit this contract →
← previous block·next block →recent activity