← previous blocknext block →recent activity
Analyzing
Block #75,514,217
16 transactions · 13 stateful · 2026-05-19 01:30:01 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,514,217 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w29w010w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x12e7c471…901c
0x34b655…2a6f
4 touches
1 conflict
0x172c5dcd…e2f2
0x065c9d…c394
2 touches
0 conflicts
0x19c959f1…5341
0x065c9d…c394
2 touches
0 conflicts
0x208991ee…e76b
0x065c9d…c394
2 touches
0 conflicts
0xdf268f1d…9d2e
0x065c9d…c394
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
3 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity