← previous blocknext block →recent activity
Analyzing
Block #76,213,763
11 transactions · 9 stateful · 2026-05-22 07:13:50 UTC
Parallelism
45/100
Blocked
56%
Avg conflicts / tx
1.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,213,763 · 11 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 conflicts
0x707a047e…1dc1
0x34b655…2a6f
8 touches
6 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
8 touches
6 conflicts
0xedb848fe…6534
0x34b655…2a6f
8 touches
6 conflicts
0x7cbd466f…1700
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x9be2b99a…a959
0x34b655…2a6f
6 touches
3 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xf853eb8e72…d84027
Audit this contract →
← previous block·next block →recent activity