← previous blocknext block →recent activity
Analyzing
Block #106,931,968
23 transactions · 22 stateful · 2026-09-22 03:48:38 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,931,968 · 23 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
3w04w15w09w010w111w212w313w414w215w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1b40f29…9b9d
0x34b655…2a6f
12 touches
15 conflicts
0x04994ed2…9032
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x743f0e02…73ec
0x34b655…2a6f
10 touches
10 conflicts
0x69168e33…6e1f
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xd1b40f2924…ae9b9d
Audit this contract →
← previous block·next block →recent activity