← previous blocknext block →recent activity
Analyzing
Block #106,100,717
25 transactions · 24 stateful · 2026-09-19 06:03:55 UTC
Parallelism
72/100
Blocked
42%
Avg conflicts / tx
1.08
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,100,717 · 25 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
1w02w13w04w06w17w18w09w113w115w218w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35bf9d78…28bd
0x34b655…2a6f
10 touches
10 conflicts
0x9ba10aad…9bc5
0x34b655…2a6f
10 touches
10 conflicts
0xdc90bed5…58a9
0x34b655…2a6f
8 touches
6 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x51581c55…b7ac
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
10 conflicts on slot 0x35bf9d78cb…7228bd
Audit this contract →
← previous block·next block →recent activity