← previous blocknext block →recent activity
Analyzing
Block #76,527,188
12 transactions · 10 stateful · 2026-05-23 18:00:55 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,527,188 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf853eb8e…4027
0x34b655…2a6f
8 touches
6 conflicts
0x77905798…fe3d
0x34b655…2a6f
6 touches
3 conflicts
0xdf889704…8950
0x34b655…2a6f
6 touches
3 conflicts
0x8a85cf3d…2868
0x34b655…2a6f
6 touches
3 conflicts
0x1c913164…5c2e
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x6eba5e7f…4b52
0x34b655…2a6f
4 touches
1 conflict
0x75f6889e…7f1e
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xf853eb8e72…d84027
Audit this contract →
← previous block·next block →recent activity