← previous blocknext block →recent activity
Analyzing
Block #74,948,604
10 transactions · 10 stateful · 2026-05-16 10:24:02 UTC
Parallelism
60/100
Blocked
30%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,948,604 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xc6417de0…2191
0xc8689a…ee79
6 touches
3 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
6 touches
3 conflicts
0x9be2b99a…a959
0x34b655…2a6f
6 touches
3 conflicts
0xaa3492db…3703
0x34b655…2a6f
6 touches
3 conflicts
0xb378025c…30cf
0x34b655…2a6f
6 touches
3 conflicts
0xd49762c9…1359
0x34b655…2a6f
6 touches
3 conflicts
0x50e10826…843b
0x8d66a4…3095
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
6 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity