← previous blocknext block →recent activity
Analyzing
Block #74,610,254
20 transactions · 19 stateful · 2026-05-14 20:45:44 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,610,254 · 20 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
3w07w110w211w012w113w214w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xbad68552…e6bf
0x34b655…2a6f
12 touches
15 conflicts
0x816881fb…e436
0x34b655…2a6f
10 touches
10 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
8 touches
6 conflicts
0xfd784183…67bb
0x34b655…2a6f
7 touches
6 conflicts
0x4d3e58e0…a2d7
0x34b655…2a6f
7 touches
6 conflicts
0xfe3d37ee…6e67
0x34b655…2a6f
6 touches
3 conflicts
0x18b81ade…81be
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: Perpl
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity