← previous blocknext block →recent activity
Analyzing
Block #73,271,124
20 transactions · 17 stateful · 2026-05-08 15:48:28 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,271,124 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w19w111w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
10 touches
10 conflicts
0x0b390c61…dc07
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xd821ae10…fe17
0xc8689a…ee79
4 touches
1 conflict
0x3e4b8d9f…b8a7
0xaba216…a862
4 touches
1 conflict
0xc5564f8e…f4bf
0xaba216…a862
4 touches
1 conflict
0xeb27550d…6028
0xaba216…a862
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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity