← previous blocknext block →recent activity
Analyzing
Block #76,225,222
19 transactions · 18 stateful · 2026-05-22 08:30:27 UTC
Parallelism
47/100
Blocked
56%
Avg conflicts / tx
2.05
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #76,225,222 · 19 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w616w718w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
16 touches
28 conflicts
0xc6417de0…2191
0xc8689a…ee79
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
14 touches
21 conflicts
0x9cc607d0…c9c7
0x34b655…2a6f
14 touches
21 conflicts
0xf4da64f8…3253
0x34b655…2a6f
10 touches
10 conflicts
0xb3a0d95e…b537
0x34b655…2a6f
10 touches
10 conflicts
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0x388e001a16…e57e04
Audit this contract →
← previous block·next block →recent activity