← previous blocknext block →recent activity
Analyzing
Block #101,064,049
18 transactions · 16 stateful · 2026-09-01 14:18:32 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,064,049 · 18 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
5w06w07w111w112w214w317w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2827ae77…4368
0x34b655…2a6f
6 touches
3 conflicts
0x8c189ee3…a18b
0x34b655…2a6f
6 touches
3 conflicts
0xf9874e36…beed
0x34b655…2a6f
4 touches
1 conflict
0xea559e7b…41f4
0x34b655…2a6f
4 touches
1 conflict
0xf06cb710…1a9a
0x34b655…2a6f
4 touches
1 conflict
0xf95af310…e380
0x34b655…2a6f
4 touches
1 conflict
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0x4bf59d22…00de
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 0x2827ae778d…a84368
Audit this contract →
← previous block·next block →recent activity