← previous blocknext block →recent activity
Analyzing
Block #106,464,059
39 transactions · 37 stateful · 2026-09-20 12:32:38 UTC
Parallelism
56/100
Blocked
57%
Avg conflicts / tx
3.28
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,464,059 · 39 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w410w111w212w313w414w515w520w621w722w823w924w1025w1126w1227w1334w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1927b58…f161
0x34b655…2a6f
28 touches
91 conflicts
0xccebffb7…fe9c
0x34b655…2a6f
28 touches
91 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
14 touches
21 conflicts
0x8658e37f…71ef
0x34b655…2a6f
12 touches
15 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
10 touches
10 conflicts
0xe098738f…9bbe
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x1b25f260…c429
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
91 conflicts on slot 0xb1927b5859…36f161
Audit this contract →
← previous block·next block →recent activity