← previous blocknext block →recent activity
Analyzing
Block #76,438,046
23 transactions · 19 stateful · 2026-05-23 08:07:27 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,438,046 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w27w38w111w113w216w320w021w122w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4770b8f7…3f75
0x34b655…2a6f
10 touches
10 conflicts
0xa5aa339f…2f4f
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x313f2565…5b00
0x34b655…2a6f
8 touches
6 conflicts
0x57de3828…3fbb
0x34b655…2a6f
8 touches
6 conflicts
0x66d236b8…a1ac
0x34b655…2a6f
8 touches
6 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
8 touches
6 conflicts
0x9cc607d0…c9c7
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
10 conflicts on slot 0x4770b8f7eb…383f75
Audit this contract →
← previous block·next block →recent activity