← previous blocknext block →recent activity
Analyzing
Block #74,528,364
47 transactions · 39 stateful · 2026-05-14 11:35:14 UTC
Parallelism
70/100
Blocked
69%
Avg conflicts / tx
2.51
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #74,528,364 · 47 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
1w02w13w25w07w08w19w210w311w412w513w614w715w816w917w1032w133w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xbb12db23…857e
0x34b655…2a6f
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: 0xab35264b…1cfa38
55 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity