← previous blocknext block →recent activity
Analyzing
Block #74,587,386
40 transactions · 17 stateful · 2026-05-14 18:12:28 UTC
Parallelism
85/100
Blocked
53%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,587,386 · 40 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w020w122w123w024w125w226w327w428w530w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
10 touches
10 conflicts
0xd49762c9…1359
0x34b655…2a6f
8 touches
6 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
8 touches
6 conflicts
0x9f9c0ebc…7797
0x34b655…2a6f
8 touches
6 conflicts
0x7b97d40a…09ed
0x34b655…2a6f
8 touches
6 conflicts
0x0711ec2d…d973
0x34b655…2a6f
8 touches
6 conflicts
0x45b9e08c…a11b
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity