← previous blocknext block →recent activity
Analyzing
Block #74,025,114
10 transactions · 8 stateful · 2026-05-12 03:44:57 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,025,114 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0c78ebcd…ca45
0x065c9d…c394
2 touches
0 conflicts
0x26a9daba…09a5
0x065c9d…c394
2 touches
0 conflicts
0x8aa773f7…e42d
0x065c9d…c394
2 touches
0 conflicts
0xb16c3d8a…97b5
0x065c9d…c394
2 touches
0 conflicts
0xdb4c3d57…f5da
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
1 conflict on slot 0x0b390c6160…02dc07
Audit this contract →
← previous block·next block →recent activity