← previous blocknext block →recent activity
Analyzing
Block #101,797,769
11 transactions · 11 stateful · 2026-09-04 03:50:06 UTC
Parallelism
55/100
Blocked
45%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,797,769 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffa7f56e…9b6a
0x34b655…2a6f
8 touches
6 conflicts
0x711ceb8d…5202
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9ca6fa7b…aeb3
0x34b655…2a6f
4 touches
1 conflict
0xb73a5ffd…ddee
0x34b655…2a6f
4 touches
1 conflict
0xb826ef15…d248
0x34b655…2a6f
4 touches
1 conflict
0xc0f6895c…e428
0x34b655…2a6f
4 touches
1 conflict
0x4089d428…b018
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
6 conflicts on slot 0xffa7f56e95…bc9b6a
Audit this contract →
← previous block·next block →recent activity