← previous blocknext block →recent activity
Analyzing
Block #75,717,673
14 transactions · 10 stateful · 2026-05-20 00:08:27 UTC
Parallelism
71/100
Blocked
30%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,717,673 · 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
4w05w16w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7b446d2…2006
0x34b655…2a6f
8 touches
6 conflicts
0x134fa1c2…606a
0x34b655…2a6f
6 touches
3 conflicts
0x35b65947…44d1
0xc8689a…ee79
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x674c1ed4…da3f
0x34b655…2a6f
6 touches
3 conflicts
0x75f928fc…0465
0x34b655…2a6f
6 touches
3 conflicts
0x904fc3c0…00ec
0x34b655…2a6f
6 touches
3 conflicts
0xcd8318c4…3e90
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 0xb7b446d20b…4f2006
Audit this contract →
← previous block·next block →recent activity