← previous blocknext block →recent activity
Analyzing
Block #75,507,275
17 transactions · 12 stateful · 2026-05-19 00:42:24 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,507,275 · 17 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
3w04w05w18w09w110w211w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x9bf064a6…4f04
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd39c6820…1546
0x065c9d…c394
4 touches
1 conflict
0x12a5dbfc…1698
0x065c9d…c394
3 touches
1 conflict
0x10d80fee…dbda
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: Perpl
6 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity