← previous blocknext block →recent activity
Analyzing
Block #74,293,474
10 transactions · 6 stateful · 2026-05-13 09:29:57 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,293,474 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0xd1456fdc…9c40
0x065c9d…c394
3 touches
1 conflict
0x89f127c2…72de
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x33346fc8…fc57
0x065c9d…c394
2 touches
0 conflicts
0x57c8e9d6…a6a7
0x065c9d…c394
2 touches
0 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
2 touches
0 conflicts
0x765c236f…ff45
0x2a68ba…90c5
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
1 conflict on slot 0xf823e97fa0…262ee6
Audit this contract →
← previous block·next block →recent activity