← previous blocknext block →recent activity
Analyzing
Block #74,525,075
20 transactions · 17 stateful · 2026-05-14 11:13:04 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,525,075 · 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
5w06w19w010w112w013w114w215w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0xf3d10975…0d07
0x34b655…2a6f
12 touches
15 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
12 touches
15 conflicts
0xa02838a3…bc54
0x34b655…2a6f
10 touches
10 conflicts
0xbc04d98e…a484
0x34b655…2a6f
7 touches
6 conflicts
0xab621973…cc16
0x34b655…2a6f
7 touches
6 conflicts
0xd11dc26e…59ab
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