← previous blocknext block →recent activity
Analyzing
Block #106,428,246
22 transactions · 22 stateful · 2026-09-20 09:32:19 UTC
Parallelism
64/100
Blocked
64%
Avg conflicts / tx
2.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,428,246 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w18w29w310w311w212w313w414w515w616w718w320w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc412a0b2…b15f
0x34b655…2a6f
16 touches
28 conflicts
0x30ceaa11…f481
0x34b655…2a6f
14 touches
21 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
10 touches
10 conflicts
0x74e46435…fdcd
0x34b655…2a6f
10 touches
10 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
10 touches
10 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x588380ee…0a5c
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 0xc412a0b278…aab15f
Audit this contract →
← previous block·next block →recent activity