← previous blocknext block →recent activity
Analyzing
Block #76,465,649
9 transactions · 7 stateful · 2026-05-23 11:11:08 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,465,649 · 9 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
3w04w15w07w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0x76e96198…eec4
0x2a68ba…90c5
2 touches
0 conflicts
0x1e9cfde1…02a6
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x993c51ed…7e3f
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity