← previous blocknext block →recent activity
Analyzing
Block #75,941,263
12 transactions · 11 stateful · 2026-05-21 00:58:43 UTC
Parallelism
58/100
Blocked
36%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,941,263 · 12 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
1w03w17w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x443a3e47…f4a4
0x065c9d…c394
8 touches
6 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
8 touches
6 conflicts
0xbe7dd2f3…cb2a
0x065c9d…c394
6 touches
5 conflicts
0x1fff6dcb…b3f4
0xc8689a…ee79
4 touches
1 conflict
0x06e40499…165e
0x1d1325…2305
4 touches
1 conflict
0xa17ec269…7cdd
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity