← previous blocknext block →recent activity
Analyzing
Block #74,332,008
46 transactions · 29 stateful · 2026-05-13 13:46:14 UTC
Parallelism
63/100
Blocked
69%
Avg conflicts / tx
2.43
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #74,332,008 · 46 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w019w020w121w222w323w424w525w626w727w832w137w939w1141w1342w1443w1545w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
26 touches
78 conflicts
0xf853eb8e…4027
0x34b655…2a6f
20 touches
45 conflicts
0x313f2565…5b00
0x34b655…2a6f
18 touches
36 conflicts
0x57de3828…3fbb
0x34b655…2a6f
18 touches
36 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0xc6417de0…2191
0xc8689a…ee79
18 touches
36 conflicts
0x2fe4467b…dd70
0x34b655…2a6f
18 touches
36 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
18 touches
36 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
78 conflicts on slot 0xa91c899f02…fa6ee3
Audit this contract →
← previous block·next block →recent activity