← previous blocknext block →recent activity
Analyzing
Block #74,353,905
40 transactions · 39 stateful · 2026-05-13 16:11:49 UTC
Parallelism
57/100
Blocked
51%
Avg conflicts / tx
2.85
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #74,353,905 · 40 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w214w015w117w018w119w220w321w422w523w624w725w832w934w1135w1237w1438w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62d080e9…4a7c
0x34b655…2a6f
26 touches
78 conflicts
0xf10e4ac5…2f88
0x34b655…2a6f
20 touches
45 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0xba85143e…a3e5
0x34b655…2a6f
18 touches
36 conflicts
0xf853eb8e…4027
0x34b655…2a6f
18 touches
36 conflicts
0x908d4442…2c4b
0x34b655…2a6f
16 touches
28 conflicts
0xaa3492db…3703
0x34b655…2a6f
16 touches
28 conflicts
0xaef9058e…322a
0x34b655…2a6f
16 touches
28 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
78 conflicts on slot 0x62d080e928…5a4a7c
Audit this contract →
← previous block·next block →recent activity