← previous blocknext block →recent activity
Analyzing
Block #76,090,807
19 transactions · 15 stateful · 2026-05-21 17:35:08 UTC
Parallelism
84/100
Blocked
40%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,090,807 · 19 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
1w03w04w15w06w110w011w112w213w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf9f153d3…a30c
0xa6afd3…d132
4 touches
1 conflict
0xaa47606d…91cb
0x9f3832…4ae4
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0xaa47606d…91ca
0x9f3832…4ae4
4 touches
1 conflict
0x2eafd046…57f8
0x34b655…2a6f
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity