← previous blocknext block →recent activity
Analyzing
Block #76,550,661
19 transactions · 16 stateful · 2026-05-23 20:37:18 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,550,661 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w38w412w013w114w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xfd7e7bd2…0c82
0xd32edf…ff58
5 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x5149ba0e…d954
0x754704…b603
4 touches
1 conflict
0xd58b5c38…3b7c
0x754704…b603
4 touches
1 conflict
0xa0bd005c…fd02
0xa6afd3…d132
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity