← previous blocknext block →recent activity
Analyzing
Block #74,920,113
33 transactions · 30 stateful · 2026-05-16 07:13:32 UTC
Parallelism
45/100
Blocked
70%
Avg conflicts / tx
3.03
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #74,920,113 · 33 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w29w010w111w212w313w414w515w616w717w818w919w1020w1125w132w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
24 touches
66 conflicts
0x19fe117b…bf8a
0x34b655…2a6f
14 touches
21 conflicts
0x388e001a…7e04
0x34b655…2a6f
14 touches
21 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
14 touches
21 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
14 touches
21 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
14 touches
21 conflicts
0xeb0915f1…c150
0x34b655…2a6f
14 touches
21 conflicts
0xafd59af5…5257
0xc8689a…ee79
14 touches
21 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
66 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity