← previous blocknext block →recent activity
Analyzing
Block #75,863,071
15 transactions · 12 stateful · 2026-05-20 16:18:19 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,863,071 · 15 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
2w03w17w28w39w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0xf4f7c688…4665
0x065c9d…c394
4 touches
1 conflict
0xaba60fa0…4675
0x065c9d…c394
4 touches
1 conflict
0x31330242…a7bf
0x065c9d…c394
3 touches
1 conflict
0xe6668d73…1da9
0x065c9d…c394
3 touches
1 conflict
0xb34808eb…6316
0x065c9d…c394
3 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
3 conflicts on slot 0x5f77d60791…b12c84
Audit this contract →
← previous block·next block →recent activity