← previous blocknext block →recent activity
Analyzing
Block #101,797,183
11 transactions · 11 stateful · 2026-09-04 03:47:09 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,797,183 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7daf6443…fd36
0x34b655…2a6f
6 touches
3 conflicts
0xe6875750…9542
0x34b655…2a6f
6 touches
3 conflicts
0xc0f6895c…e428
0x34b655…2a6f
6 touches
3 conflicts
0xb73a5ffd…ddee
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0ffac39e…6d34
0x34b655…2a6f
4 touches
1 conflict
0x15698ac9…2a46
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
3 conflicts on slot 0x7daf644369…48fd36
Audit this contract →
← previous block·next block →recent activity