← previous blocknext block →recent activity
Analyzing
Block #74,451,710
7 transactions · 7 stateful · 2026-05-14 03:02:52 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,451,710 · 7 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
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xe6e91a85…94b8
0x065c9d…c394
4 touches
1 conflict
0x6b653867…7105
0x065c9d…c394
3 touches
1 conflict
0x059db4ed…9594
0x065c9d…c394
2 touches
0 conflicts
0x71ffdb10…1fb5
0x065c9d…c394
2 touches
0 conflicts
0x793837f9…76c5
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity