← previous blocknext block →recent activity
Analyzing
Block #74,023,941
10 transactions · 8 stateful · 2026-05-12 03:37:10 UTC
Parallelism
70/100
Blocked
25%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,023,941 · 10 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
1w04w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x7a11d92d…f5c2
0x065c9d…c394
2 touches
0 conflicts
0xa8fdbe7b…4b15
0x065c9d…c394
2 touches
0 conflicts
0xcd450a8e…a8af
0x065c9d…c394
2 touches
0 conflicts
0xd299890b…446f
0x065c9d…c394
2 touches
0 conflicts
0xdf311005…c61a
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