← previous blocknext block →recent activity
Analyzing
Block #76,462,640
30 transactions · 29 stateful · 2026-05-23 10:51:03 UTC
Parallelism
43/100
Blocked
66%
Avg conflicts / tx
4.2
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #76,462,640 · 30 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
2w04w16w07w18w29w310w411w512w613w714w815w916w1017w1118w1219w225w1226w1328w1529w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c913164…5c2e
0x34b655…2a6f
26 touches
78 conflicts
0xc6417de0…2191
0xc8689a…ee79
24 touches
66 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0xedb848fe…6534
0x34b655…2a6f
20 touches
45 conflicts
0x57de3828…3fbb
0x34b655…2a6f
20 touches
45 conflicts
0x6137fa69…4209
0x34b655…2a6f
16 touches
28 conflicts
0x493e94e2…7950
0x34b655…2a6f
12 touches
15 conflicts
0xf853eb8e…4027
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
78 conflicts on slot 0x1c913164f5…845c2e
Audit this contract →
← previous block·next block →recent activity