← previous blocknext block →recent activity
Analyzing
Block #74,285,365
14 transactions · 11 stateful · 2026-05-13 08:35:56 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,285,365 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9d2cf20…a668
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x6423a16a…fff4
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x88e1d863…c925
0x34b655…2a6f
4 touches
1 conflict
0xad63585b…768d
0x34b655…2a6f
4 touches
1 conflict
0x0520da1d…c88e
0x34b655…2a6f
4 touches
1 conflict
0x35b65947…44d1
0xc8689a…ee79
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
3 conflicts on slot 0xb9d2cf2005…28a668
Audit this contract →
← previous block·next block →recent activity