← previous blocknext block →recent activity
Analyzing
Block #75,741,614
9 transactions · 7 stateful · 2026-05-20 02:47:48 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,741,614 · 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
1w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5f2b1e7…4510
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0xfcc44fd7…e1ef
0x065c9d…c394
3 touches
1 conflict
0x04b40d5e…2c0e
0x065c9d…c394
3 touches
1 conflict
0x1a97a373…4447
0x065c9d…c394
2 touches
0 conflicts
0x68975685…7c21
0x065c9d…c394
2 touches
0 conflicts
0x7d3cd397…102d
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xa5f2b1e75e…ce4510
Audit this contract →
← previous block·next block →recent activity