← previous blocknext block →recent activity
Analyzing
Block #76,174,232
11 transactions · 11 stateful · 2026-05-22 02:50:48 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,174,232 · 11 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
2w03w14w25w26w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
6 touches
3 conflicts
0x1fff6dcb…b3f4
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x8488f10f…9354
0x1d1325…2305
4 touches
1 conflict
0x8488f10f…9355
0x1d1325…2305
4 touches
1 conflict
0x8488f10f…9356
0x1d1325…2305
4 touches
1 conflict
0xa605468c…1bfc
0x1d1325…2305
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 0xf3d7a307cc…f14d63
Audit this contract →
← previous block·next block →recent activity