← previous blocknext block →recent activity
Analyzing
Block #76,482,961
21 transactions · 16 stateful · 2026-05-23 13:06:28 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,482,961 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b97d40a…09ed
0x34b655…2a6f
14 touches
21 conflicts
0x1c913164…5c2e
0x34b655…2a6f
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
14 touches
21 conflicts
0xf853eb8e…4027
0x34b655…2a6f
14 touches
21 conflicts
0xc6417de0…2191
0xc8689a…ee79
14 touches
21 conflicts
0x9cc607d0…c9c7
0x34b655…2a6f
14 touches
21 conflicts
0x45b9e08c…a11b
0x34b655…2a6f
13 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
21 conflicts on slot 0x7b97d40a0c…6409ed
Audit this contract →
← previous block·next block →recent activity