← previous blocknext block →recent activity
Analyzing
Block #106,566,016
23 transactions · 21 stateful · 2026-09-20 21:05:45 UTC
Parallelism
65/100
Blocked
52%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,566,016 · 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
1w02w13w04w05w17w08w112w113w215w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f505f44…3c6d
0x34b655…2a6f
12 touches
15 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe0cdd08b…6a06
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 conflicts
0xbcbd3c37…7f24
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
15 conflicts on slot 0x5f505f4444…af3c6d
Audit this contract →
← previous block·next block →recent activity