← previous blocknext block →recent activity
Analyzing
Block #74,334,347
21 transactions · 18 stateful · 2026-05-13 14:01:49 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,334,347 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w415w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xda1f3e2c…b73d
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xf3981be5…2c47
0x34b655…2a6f
6 touches
3 conflicts
0x9b8800c1…ed12
0x34b655…2a6f
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x4d3e58e0…a2d7
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity