← previous blocknext block →recent activity
Analyzing
Block #76,290,919
13 transactions · 12 stateful · 2026-05-22 15:47:40 UTC
Parallelism
39/100
Blocked
67%
Avg conflicts / tx
2.08
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #76,290,919 · 13 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w48w110w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe54a1f6f…18f2
0x34b655…2a6f
12 touches
15 conflicts
0x7cbd466f…1700
0x34b655…2a6f
12 touches
15 conflicts
0xf853eb8e…4027
0x34b655…2a6f
12 touches
15 conflicts
0x41a10fb4…e4e1
0x34b655…2a6f
12 touches
15 conflicts
0x313f2565…5b00
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
10 touches
10 conflicts
0x9cc607d0…c9c7
0x34b655…2a6f
10 touches
10 conflicts
0xaef9058e…322a
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
15 conflicts on slot 0xe54a1f6fdd…7918f2
Audit this contract →
← previous block·next block →recent activity