← previous blocknext block →recent activity
Analyzing
Block #74,384,302
9 transactions · 7 stateful · 2026-05-13 19:34:11 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,384,302 · 9 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x556bf24a…9341
0x065c9d…c394
4 touches
1 conflict
0xe4a926e8…2b48
0x065c9d…c394
3 touches
1 conflict
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x42c7a32d…e828
0x065c9d…c394
2 touches
0 conflicts
0x0872abbe…9c39
0x2a68ba…90c5
2 touches
0 conflicts
0x194f2c02…19e6
0x2a68ba…90c5
2 touches
0 conflicts
0x76e559a4…77fb
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity