← previous blocknext block →recent activity
Analyzing
Block #76,244,032
21 transactions · 16 stateful · 2026-05-22 10:35:46 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,244,032 · 21 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
1w02w13w24w35w36w07w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x73912233…4589
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1f3b37cb…357f
0x065c9d…c394
4 touches
1 conflict
0x3ecca7e0…313c
0x065c9d…c394
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: 0xab35264b…1cfa38
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity