← previous blocknext block →recent activity
Analyzing
Block #74,761,026
31 transactions · 24 stateful · 2026-05-15 13:31:52 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
1.48
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #74,761,026 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w18w29w010w011w112w213w314w415w516w618w119w120w325w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
14 touches
21 conflicts
0x3b0f5871…74dd
0x34b655…2a6f
10 touches
10 conflicts
0x5d70606a…1d53
0x34b655…2a6f
8 touches
6 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
8 touches
6 conflicts
0x9be2b99a…a959
0x34b655…2a6f
8 touches
6 conflicts
0xa009aa7b…a5ba
0x34b655…2a6f
8 touches
6 conflicts
0xc6417de0…2191
0xc8689a…ee79
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
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity