← previous blocknext block →recent activity
Analyzing
Block #76,089,851
16 transactions · 14 stateful · 2026-05-21 17:28:45 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,089,851 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0xf9f153d3…a30c
0xa6afd3…d132
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x82404502…e085
0x065c9d…c394
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x7d5eab43…8017
0xd32edf…ff58
3 touches
1 conflict
0x60b24061…7c23
0x188d58…ea8e
2 touches
0 conflicts
0x60b24061…7c25
0x188d58…ea8e
2 touches
0 conflicts
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
1 conflict on slot 0x0aa885fa2f…33a3d1
Audit this contract →
← previous block·next block →recent activity