← previous blocknext block →recent activity
Analyzing
Block #74,788,742
31 transactions · 19 stateful · 2026-05-15 16:37:20 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,788,742 · 31 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
2w03w118w019w120w221w327w028w129w2
- 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
0x038aa895…2f47
0x34b655…2a6f
6 touches
3 conflicts
0x0711ec2d…d973
0x34b655…2a6f
6 touches
3 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
6 touches
3 conflicts
0x32ee90db…decc
0x34b655…2a6f
6 touches
3 conflicts
0x388e001a…7e04
0x34b655…2a6f
6 touches
3 conflicts
0xedb848fe…6534
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity