← previous blocknext block →recent activity
Analyzing
Block #75,024,214
11 transactions · 10 stateful · 2026-05-16 18:50:18 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,024,214 · 11 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
1w02w14w05w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd1a0adf6…6e55
0x54cd53…9e7d
2 touches
0 conflicts
0x0600bbd2…6b4b
0x6657d1…8ccc
2 touches
0 conflicts
0x084d205b…c4bb
0x6657d1…8ccc
2 touches
0 conflicts
0x15d6fe18…6e33
0x6657d1…8ccc
2 touches
0 conflicts
0x2a7174c8…7e09
0x6657d1…8ccc
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity