← previous blocknext block →recent activity
Analyzing
Block #76,416,505
15 transactions · 11 stateful · 2026-05-23 05:44:04 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,416,505 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0x279e658f…de3d
0x96b79e…d00a
4 touches
1 conflict
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0xcab2b82c…47bc
0x34b655…2a6f
4 touches
1 conflict
0x138aa8a0…71d6
0x34b655…2a6f
2 touches
0 conflicts
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x25de453d…9573
0x34b655…2a6f
2 touches
0 conflicts
0x391a9dcb…edac
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xf9b8ae99dc…3532b3
Audit this contract →
← previous block·next block →recent activity