← previous blocknext block →recent activity
Analyzing
Block #106,413,114
30 transactions · 25 stateful · 2026-09-20 08:16:10 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.67
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,413,114 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w012w116w217w318w419w521w622w723w824w928w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd131fa…dbdb
0x34b655…2a6f
16 touches
28 conflicts
0x74e46435…fdcd
0x34b655…2a6f
12 touches
15 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x0f270a31…640c
0x34b655…2a6f
8 touches
6 conflicts
0x1b662182…c900
0x34b655…2a6f
8 touches
6 conflicts
0x5f1ffb67…59a2
0x34b655…2a6f
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: Perpl
28 conflicts on slot 0xfdd131fae1…f8dbdb
Audit this contract →
← previous block·next block →recent activity