← previous blocknext block →recent activity
Analyzing
Block #74,416,331
41 transactions · 33 stateful · 2026-05-13 23:07:21 UTC
Parallelism
66/100
Blocked
73%
Avg conflicts / tx
2.22
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #74,416,331 · 41 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w111w012w113w214w315w416w517w618w734w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
16 touches
28 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
10 touches
10 conflicts
0x1c389468…6b0e
0x34b655…2a6f
10 touches
10 conflicts
0x5675c293…17d9
0x34b655…2a6f
8 touches
6 conflicts
0xc3aacf13…6b3d
0x34b655…2a6f
8 touches
6 conflicts
0xac8e97a0…8426
0x34b655…2a6f
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
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity