← previous blocknext block →recent activity
Analyzing
Block #106,789,886
28 transactions · 24 stateful · 2026-09-21 15:53:28 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,789,886 · 28 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
1w02w05w06w17w28w09w111w012w013w114w015w116w220w021w322w123w226w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x16d77246…bac5
0x34b655…2a6f
6 touches
3 conflicts
0x280aaa58…1c52
0x34b655…2a6f
6 touches
3 conflicts
0x34dad526…5f98
0x34b655…2a6f
6 touches
3 conflicts
0x7e4ebdbe…0e9f
0x34b655…2a6f
6 touches
3 conflicts
0x8e7fd942…c379
0x34b655…2a6f
6 touches
3 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
6 touches
3 conflicts
0xb7e8b0c4…dec3
0x34b655…2a6f
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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity