← previous blocknext block →recent activity
Analyzing
Block #76,225,983
18 transactions · 17 stateful · 2026-05-22 08:35:32 UTC
Parallelism
67/100
Blocked
65%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,225,983 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w08w19w210w311w412w313w217w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0380ead4…3a27
0x34b655…2a6f
10 touches
10 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
10 touches
10 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x9cc607d0…c9c7
0x34b655…2a6f
8 touches
6 conflicts
0xfd314139…0b72
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
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
10 conflicts on slot 0x0380ead401…853a27
Audit this contract →
← previous block·next block →recent activity