← previous blocknext block →recent activity
Analyzing
Block #106,932,541
23 transactions · 20 stateful · 2026-09-22 03:51:31 UTC
Parallelism
57/100
Blocked
60%
Avg conflicts / tx
2.04
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,932,541 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w010w311w412w513w614w717w318w419w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc844ab5…4c6d
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0xedfd12b0…dba4
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0xfbabe7cb…68ef
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
28 conflicts on slot 0xcc844ab542…814c6d
Audit this contract →
← previous block·next block →recent activity