← previous blocknext block →recent activity
Analyzing
Block #76,522,250
13 transactions · 11 stateful · 2026-05-23 17:28:02 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,522,250 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa0d0542…d8ec
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf0d3c3f0…c09e
0xa6afd3…d132
4 touches
1 conflict
0x1dad5c49…fa05
0xa6afd3…d132
3 touches
1 conflict
0x44b8fa25…43be
0xa6afd3…d132
3 touches
1 conflict
0x439d4fef…41e2
0x065c9d…c394
2 touches
0 conflicts
0x56c94ca5…507c
0x065c9d…c394
2 touches
0 conflicts
0x8847c203…e4ac
0x065c9d…c394
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 0xaa0d054297…bdd8ec
Audit this contract →
← previous block·next block →recent activity