← previous blocknext block →recent activity
Analyzing
Block #106,100,749
28 transactions · 25 stateful · 2026-09-19 06:04:05 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,100,749 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w07w210w013w014w217w119w220w321w422w525w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcc8f826…7c5f
0x34b655…2a6f
8 touches
6 conflicts
0x2e92ee18…916e
0x34b655…2a6f
8 touches
6 conflicts
0x9ba10aad…9bc5
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x73912233…4586
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xbf756c9b…2dbd
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: Perpl
6 conflicts on slot 0xfcc8f826d7…5f7c5f
Audit this contract →
← previous block·next block →recent activity