← previous blocknext block →recent activity
Analyzing
Block #76,112,555
36 transactions · 29 stateful · 2026-05-21 19:59:59 UTC
Parallelism
61/100
Blocked
66%
Avg conflicts / tx
2.08
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #76,112,555 · 36 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w110w213w014w115w216w017w118w219w320w421w522w623w724w825w926w1027w330w233w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0xc6417de0…2191
0xc8689a…ee79
12 touches
15 conflicts
0x388e001a…7e04
0x34b655…2a6f
12 touches
15 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
12 touches
15 conflicts
0x908d4442…2c4b
0x34b655…2a6f
12 touches
15 conflicts
0x99f080dc…58c1
0x34b655…2a6f
12 touches
15 conflicts
0x9be2b99a…a959
0x34b655…2a6f
12 touches
15 conflicts
0xf853eb8e…4027
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity