← previous blocknext block →recent activity
Analyzing
Block #75,419,798
13 transactions · 10 stateful · 2026-05-18 14:54:11 UTC
Parallelism
77/100
Blocked
30%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,419,798 · 13 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
1w05w16w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4a2f02aa…fdac
0x065c9d…c394
2 touches
0 conflicts
0x5bf9e26b…9e6e
0x065c9d…c394
2 touches
0 conflicts
0x7992c325…cdcb
0x065c9d…c394
2 touches
0 conflicts
0x805e109d…11c5
0x065c9d…c394
2 touches
0 conflicts
0x85cc0a57…1612
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