← previous blocknext block →recent activity
Analyzing
Block #76,223,280
13 transactions · 11 stateful · 2026-05-22 08:17:23 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,223,280 · 13 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
1w02w13w04w16w27w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0aa885fa…a3d1
0x2a68ba…90c5
6 touches
3 conflicts
0xd624a621…0610
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x41bdbab0…e39f
0xd32edf…ff58
3 touches
1 conflict
0x679c051f…b678
0x065c9d…c394
3 touches
1 conflict
0x679c051f…b679
0x065c9d…c394
3 touches
1 conflict
0x7a730ba5…fb4f
0x065c9d…c394
3 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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x0aa885fa2f…33a3d1
Audit this contract →
← previous block·next block →recent activity