← previous blocknext block →recent activity
Analyzing
Block #75,269,819
18 transactions · 16 stateful · 2026-05-17 22:10:02 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,269,819 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w110w311w412w516w017w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x6b319071…a105
0xc8689a…ee79
8 touches
6 conflicts
0xbb2a8a4e…f4bb
0x065c9d…c394
8 touches
6 conflicts
0xf3d7a307…4d63
0x065c9d…c394
8 touches
6 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
8 touches
6 conflicts
0x2cc957b8…cddf
0x065c9d…c394
7 touches
6 conflicts
0xf0f673fd…37a7
0x5d823e…89c6
6 touches
3 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
6 touches
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity