← previous blocknext block →recent activity
Analyzing
Block #74,600,889
34 transactions · 19 stateful · 2026-05-14 19:43:03 UTC
Parallelism
88/100
Blocked
37%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,600,889 · 34 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
1w02w112w116w019w122w023w127w028w132w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbad68552…e6bf
0x34b655…2a6f
8 touches
6 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x18b81ade…81be
0x34b655…2a6f
4 touches
1 conflict
0x3e1f7818…2fc8
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
0x34b655…2a6f
4 touches
1 conflict
0xa92c8763…6d7f
0x34b655…2a6f
4 touches
1 conflict
0xec1ff44b…61ba
0x34b655…2a6f
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 0xbad6855239…f0e6bf
Audit this contract →
← previous block·next block →recent activity