← previous blocknext block →recent activity
Analyzing
Block #74,241,365
16 transactions · 14 stateful · 2026-05-13 03:43:25 UTC
Parallelism
69/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,241,365 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w28w29w310w411w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a354a63…0515
0x065c9d…c394
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x8a35acfb…d1aa
0x8d66a4…3095
4 touches
1 conflict
0x62ce6483…789b
0x065c9d…c394
4 touches
1 conflict
0x8e66da19…66b6
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
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
6 conflicts on slot 0x2a354a6333…480515
Audit this contract →
← previous block·next block →recent activity