← previous blocknext block →recent activity
Analyzing
Block #76,550,685
14 transactions · 10 stateful · 2026-05-23 20:37:28 UTC
Parallelism
71/100
Blocked
30%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,550,685 · 14 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
5w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d3e58e0…a2d7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb7b446d2…2006
0x34b655…2a6f
6 touches
3 conflicts
0x463be44a…2830
0x34b655…2a6f
4 touches
1 conflict
0x6c2052bd…25a1
0x34b655…2a6f
4 touches
1 conflict
0x8fbde2b3…9b8f
0x34b655…2a6f
4 touches
1 conflict
0xcadd9a74…8bb7
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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
3 conflicts on slot 0x4d3e58e0af…05a2d7
Audit this contract →
← previous block·next block →recent activity