← previous blocknext block →recent activity
Analyzing
Block #75,128,003
30 transactions · 22 stateful · 2026-05-17 06:22:39 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,128,003 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w26w07w18w29w317w323w124w225w327w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x631b4113…baa9
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x208c1363…c653
0x34b655…2a6f
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x41d3bfa5…523e
0x34b655…2a6f
6 touches
3 conflicts
0xc7f28b7a…5777
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
10 conflicts on slot 0x631b41138f…31baa9
Audit this contract →
← previous block·next block →recent activity