← previous blocknext block →recent activity
Analyzing
Block #74,679,783
59 transactions · 38 stateful · 2026-05-15 04:29:28 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
2.25
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #74,679,783 · 59 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w310w427w028w129w230w331w432w533w634w735w836w938w151w1452w1555w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x4381471a…9ac1
0x34b655…2a6f
12 touches
15 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
10 touches
10 conflicts
0x0d622e34…0000
0x681e90…ae09
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa02838a3…bc54
0x34b655…2a6f
8 touches
6 conflicts
0xbe2dbc0f…f95b
0xd32edf…ff58
7 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
45 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity