← previous blocknext block →recent activity
Analyzing
Block #75,756,974
19 transactions · 17 stateful · 2026-05-20 04:29:59 UTC
Parallelism
79/100
Blocked
24%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,756,974 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w211w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xdfa159d0…1576
0x065c9d…c394
8 touches
6 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
8 touches
6 conflicts
0x0aa885fa…a3d1
0x2a68ba…90c5
6 touches
3 conflicts
0x6a39e8c7…1a55
0x065c9d…c394
5 touches
4 conflicts
0xd16b9697…8b5d
0x065c9d…c394
5 touches
3 conflicts
0x604e2272…1902
0xd32edf…ff58
5 touches
3 conflicts
0xa17ec269…7cdd
0x1d1325…2305
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity