← previous blocknext block →recent activity
Analyzing
Block #76,246,037
21 transactions · 19 stateful · 2026-05-22 10:49:09 UTC
Parallelism
86/100
Blocked
37%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,246,037 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w18w09w210w212w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf282c2b3…28b4
0xa6afd3…d132
6 touches
3 conflicts
0x03226734…d6d2
0xa6afd3…d132
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x8d47c9a4…f121
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
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: 0xa6afd386…b0d132
3 conflicts on slot 0xf282c2b36a…3228b4
Audit this contract →
← previous block·next block →recent activity