← previous blocknext block →recent activity
Analyzing
Block #101,324,322
33 transactions · 26 stateful · 2026-09-02 12:08:14 UTC
Parallelism
76/100
Blocked
58%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,324,322 · 33 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
8w09w010w111w012w113w114w215w017w319w220w322w426w227w529w130w532w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7151b1ad…4520
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8ccada3a…0979
0x34b655…2a6f
8 touches
6 conflicts
0xc4d98fb1…c354
0x40c49f…2af0
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
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 0x7151b1adae…de4520
Audit this contract →
← previous block·next block →recent activity