← previous blocknext block →recent activity
Analyzing
Block #76,309,710
15 transactions · 13 stateful · 2026-05-22 17:52:42 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,309,710 · 15 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
1w02w04w15w16w19w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf282c2b3…28b4
0xa6afd3…d132
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb81
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x03226734…d6d2
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 0xf282c2b36a…3228b4
Audit this contract →
← previous block·next block →recent activity