← previous blocknext block →recent activity
Analyzing
Block #74,765,186
31 transactions · 20 stateful · 2026-05-15 13:59:45 UTC
Parallelism
87/100
Blocked
45%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,765,186 · 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
1w02w13w07w19w211w015w016w117w218w319w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xedb848fe…6534
0x34b655…2a6f
6 touches
3 conflicts
0xf853eb8e…4027
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc6417de0…2191
0xc8689a…ee79
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x9be2b99a…a959
0x34b655…2a6f
6 touches
3 conflicts
0x388e001a…7e04
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