← previous blocknext block →recent activity
Analyzing
Block #74,034,335
14 transactions · 9 stateful · 2026-05-12 04:46:04 UTC
Parallelism
79/100
Blocked
22%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,034,335 · 14 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
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x145619c0…7bc1
0x065c9d…c394
3 touches
1 conflict
0x1009dc03…6af3
0x065c9d…c394
2 touches
0 conflicts
0x16da55f7…7141
0x065c9d…c394
2 touches
0 conflicts
0x18d0e86b…ce19
0x065c9d…c394
2 touches
0 conflicts
0x376b60e6…9e44
0x065c9d…c394
2 touches
0 conflicts
0x6411ea12…7975
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