← previous blocknext block →recent activity
Analyzing
Block #73,751,126
16 transactions · 15 stateful · 2026-05-10 21:13:31 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,751,126 · 16 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
2w03w04w15w26w39w110w212w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x4d87512b…897c
0x065c9d…c394
8 touches
6 conflicts
0x22e295f5…1bef
0x065c9d…c394
8 touches
6 conflicts
0x602c9421…5a58
0xd32edf…ff58
7 touches
6 conflicts
0x50997ada…364d
0x6c4bfa…a540
4 touches
1 conflict
0xf0f673fd…37a7
0x6c4bfa…a540
4 touches
1 conflict
0xed57bddf…1abf
0xc8689a…ee79
4 touches
1 conflict
0x5593cc83…bed8
0x065c9d…c394
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity