← previous blocknext block →recent activity
Analyzing
Block #75,847,572
15 transactions · 13 stateful · 2026-05-20 14:34:25 UTC
Parallelism
47/100
Blocked
54%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #75,847,572 · 15 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
2w03w14w25w310w411w512w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe54a1f6f…18f2
0x34b655…2a6f
14 touches
21 conflicts
0xf853eb8e…4027
0x34b655…2a6f
12 touches
15 conflicts
0x313f2565…5b00
0x34b655…2a6f
8 touches
6 conflicts
0x57de3828…3fbb
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x23ec8cdf…ef19
0x34b655…2a6f
8 touches
6 conflicts
0x9be2b99a…a959
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xe54a1f6fdd…7918f2
Audit this contract →
← previous block·next block →recent activity