← previous blocknext block →recent activity
Analyzing
Block #101,502,853
15 transactions · 11 stateful · 2026-09-03 03:06:36 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,502,853 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w19w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x26ed4a2e…5895
0xd32edf…ff58
5 touches
3 conflicts
0x89659f43…d780
0x34b655…2a6f
4 touches
1 conflict
0x41b8d2ca…cff2
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xe18d6a4d…07a6
0x34b655…2a6f
4 touches
1 conflict
0x9bf56401…08f2
0x34b655…2a6f
4 touches
1 conflict
0x213ce19e…b5f5
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity