← previous blocknext block →recent activity
Analyzing
Block #106,422,947
21 transactions · 20 stateful · 2026-09-20 09:05:39 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,422,947 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w09w018w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cd9fd28…a158
0x34b655…2a6f
8 touches
6 conflicts
0x422bab7d…0f6c
0x34b655…2a6f
8 touches
6 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
6 touches
3 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
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
6 conflicts on slot 0x7cd9fd286f…a7a158
Audit this contract →
← previous block·next block →recent activity