← previous blocknext block →recent activity
Analyzing
Block #75,893,298
33 transactions · 23 stateful · 2026-05-20 19:39:31 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,893,298 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w07w18w09w111w218w019w120w021w122w228w129w130w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2093fe30…517f
0x34b655…2a6f
8 touches
6 conflicts
0x85a88798…f85e
0x34b655…2a6f
8 touches
6 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
6 touches
3 conflicts
0x5086c64a…28ba
0x34b655…2a6f
6 touches
3 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x35b65947…44d1
0xc8689a…ee79
6 touches
3 conflicts
0x0520da1d…c88e
0x34b655…2a6f
6 touches
3 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 0x2093fe30af…13517f
Audit this contract →
← previous block·next block →recent activity