← previous blocknext block →recent activity
Analyzing
Block #106,395,213
19 transactions · 19 stateful · 2026-09-20 06:46:06 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,395,213 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w29w210w212w313w414w515w618w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b53436c…2ec3
0x34b655…2a6f
14 touches
21 conflicts
0x4dcf06ee…b002
0x34b655…2a6f
10 touches
10 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0x74405437…666d
0x34b655…2a6f
6 touches
3 conflicts
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
0xdd9624b6…1d56
0x34b655…2a6f
4 touches
1 conflict
0x13b3e772…6835
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
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
21 conflicts on slot 0x3b53436c6f…c62ec3
Audit this contract →
← previous block·next block →recent activity