← previous blocknext block →recent activity
Analyzing
Block #76,483,696
16 transactions · 14 stateful · 2026-05-23 13:11:20 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,483,696 · 16 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
1w02w14w05w16w27w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c913164…5c2e
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x5728edaf…f1d4
0x34b655…2a6f
8 touches
6 conflicts
0x578e7f66…1b56
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
8 touches
6 conflicts
0x9cc607d0…c9c7
0x34b655…2a6f
8 touches
6 conflicts
0xc83595c6…fece
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 0x1c913164f5…845c2e
Audit this contract →
← previous block·next block →recent activity