← previous blocknext block →recent activity
Analyzing
Block #106,917,440
16 transactions · 16 stateful · 2026-09-22 02:35:31 UTC
Parallelism
56/100
Blocked
63%
Avg conflicts / tx
1.44
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,917,440 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w29w310w111w412w513w614w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85bfd0af…ce96
0x34b655…2a6f
10 touches
10 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0xf7ed92bb…24eb
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x61da5094…a3c9
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
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
10 conflicts on slot 0x85bfd0afba…f5ce96
Audit this contract →
← previous block·next block →recent activity