← previous blocknext block →recent activity
Analyzing
Block #74,765,529
30 transactions · 23 stateful · 2026-05-15 14:02:04 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,765,529 · 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
2w04w15w07w09w116w017w118w219w320w421w525w227w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0xc6417de0…2191
0xc8689a…ee79
10 touches
10 conflicts
0x36cdae67…8407
0x34b655…2a6f
10 touches
10 conflicts
0x388e001a…7e04
0x34b655…2a6f
10 touches
10 conflicts
0x57de3828…3fbb
0x34b655…2a6f
10 touches
10 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
10 touches
10 conflicts
0x9be2b99a…a959
0x34b655…2a6f
10 touches
10 conflicts
0xedb848fe…6534
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity