← previous blocknext block →recent activity
Analyzing
Block #106,944,399
26 transactions · 26 stateful · 2026-09-22 04:51:12 UTC
Parallelism
65/100
Blocked
65%
Avg conflicts / tx
2.04
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,944,399 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w311w412w513w614w715w821w524w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fad6fee…7714
0x34b655…2a6f
16 touches
28 conflicts
0x155e52ca…fac7
0x34b655…2a6f
10 touches
10 conflicts
0x361362df…4e32
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x7dd8c370…330e
0x34b655…2a6f
10 touches
10 conflicts
0x3ca49f3f…b79f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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 0x5fad6fee64…277714
Audit this contract →
← previous block·next block →recent activity