← previous blocknext block →recent activity
Analyzing
Block #74,986,671
18 transactions · 17 stateful · 2026-05-16 14:39:26 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,986,671 · 18 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
1w03w04w06w09w111w212w313w414w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
6 touches
3 conflicts
0x1f4c677f…7308
0x34b655…2a6f
6 touches
3 conflicts
0xbd934643…0cf3
0xd32edf…ff58
5 touches
3 conflicts
0xfbbfc5af…264e
0x065c9d…c394
4 touches
1 conflict
0xb4939671…fc2c
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