← previous blocknext block →recent activity
Analyzing
Block #74,287,023
9 transactions · 9 stateful · 2026-05-13 08:46:56 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,287,023 · 9 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
1w02w06w17w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0x7b7bcac3…8fbf
0x34b655…2a6f
4 touches
1 conflict
0x1d13383c…a5ad
0x065c9d…c394
2 touches
0 conflicts
0x2eaa658b…4dd5
0x065c9d…c394
2 touches
0 conflicts
0x30561315…c1c4
0x065c9d…c394
2 touches
0 conflicts
0xb50b982f…c9c7
0x065c9d…c394
2 touches
0 conflicts
0xd8a5f784…ffca
0x065c9d…c394
2 touches
0 conflicts
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity