← previous blocknext block →recent activity
Analyzing
Block #74,796,331
34 transactions · 31 stateful · 2026-05-15 17:28:00 UTC
Parallelism
71/100
Blocked
68%
Avg conflicts / tx
1.47
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #74,796,331 · 34 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
1w02w13w25w07w08w09w110w211w312w413w514w623w133w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x50a88d10…679c
0x34b655…2a6f
8 touches
6 conflicts
0x6a15f784…10b2
0x34b655…2a6f
6 touches
3 conflicts
0x3b0f5871…74dd
0x34b655…2a6f
6 touches
3 conflicts
0xd49762c9…1359
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 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: 0xab35264b…1cfa38
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity