← previous blocknext block →recent activity
Analyzing
Block #75,668,783
9 transactions · 6 stateful · 2026-05-19 18:43:17 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,668,783 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2f88a23f…9dc5
0x2a68ba…90c5
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x4795ff7a…d1fc
0x065c9d…c394
3 touches
1 conflict
0x3dca700c…13b1
0x1d1325…2305
2 touches
0 conflicts
0x5cc231f5…f1cd
0x1d1325…2305
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
1 conflict on slot 0x892daf6e5d…6d48d8
Audit this contract →
← previous block·next block →recent activity