← previous blocknext block →recent activity
Analyzing
Block #76,088,636
21 transactions · 19 stateful · 2026-05-21 17:20:40 UTC
Parallelism
62/100
Blocked
47%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #76,088,636 · 21 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
2w03w04w17w08w19w210w311w412w513w614w120w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8db1e0f2…2fcf
0x34b655…2a6f
16 touches
28 conflicts
0xf853eb8e…4027
0x34b655…2a6f
16 touches
28 conflicts
0x313f2565…5b00
0x34b655…2a6f
14 touches
21 conflicts
0x32ee90db…decc
0x34b655…2a6f
14 touches
21 conflicts
0x388e001a…7e04
0x34b655…2a6f
14 touches
21 conflicts
0xc6417de0…2191
0xc8689a…ee79
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x68728b15…33fc
0x34b655…2a6f
14 touches
21 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 0x8db1e0f2ad…b02fcf
Audit this contract →
← previous block·next block →recent activity