← previous blocknext block →recent activity
Analyzing
Block #75,791,820
16 transactions · 14 stateful · 2026-05-20 08:21:49 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,791,820 · 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
1w04w16w27w38w09w114w415w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x5f77d607…2c84
0x065c9d…c394
10 touches
10 conflicts
0x892daf6e…48d8
0x065c9d…c394
8 touches
6 conflicts
0xabc68052…c93c
0x065c9d…c394
4 touches
1 conflict
0xd36836d2…6b6a
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity