← previous blocknext block →recent activity
Analyzing
Block #75,079,217
16 transactions · 12 stateful · 2026-05-17 00:56:59 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,079,217 · 16 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
2w04w16w07w18w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x2484cc15…5afc
0x34b655…2a6f
4 touches
1 conflict
0x2965e2d6…5800
0x34b655…2a6f
4 touches
1 conflict
0x414e9446…4b59
0x34b655…2a6f
4 touches
1 conflict
0x4858af56…10ef
0x34b655…2a6f
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x85e47b79…5a70
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity