← previous blocknext block →recent activity
Analyzing
Block #75,200,369
14 transactions · 14 stateful · 2026-05-17 14:25:50 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,200,369 · 14 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
4w05w18w09w110w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2905340c…dbc6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0036
0x386489…7508
4 touches
1 conflict
0x1a920eda…bfae
0x386489…7508
4 touches
1 conflict
0x59e52fc8…1566
0x754704…b603
4 touches
1 conflict
0xa8669ab5…6af7
0x754704…b603
4 touches
1 conflict
0x00000000…0036
0x784999…1f2d
4 touches
1 conflict
0x2f417c04…a545
0x784999…1f2d
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity