← previous blocknext block →recent activity
Analyzing
Block #74,761,961
46 transactions · 34 stateful · 2026-05-15 13:38:12 UTC
Parallelism
61/100
Blocked
68%
Avg conflicts / tx
2.91
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #74,761,961 · 46 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w116w017w118w219w320w421w523w724w825w926w1029w232w136w837w939w1241w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
20 touches
45 conflicts
0x388e001a…7e04
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xc6417de0…2191
0xc8689a…ee79
16 touches
28 conflicts
0x9be2b99a…a959
0x34b655…2a6f
12 touches
15 conflicts
0x9cc607d0…c9c7
0x34b655…2a6f
12 touches
15 conflicts
0x038aa895…2f47
0x34b655…2a6f
12 touches
15 conflicts
0x38f431b8…c65d
0x34b655…2a6f
12 touches
15 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
45 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity