← previous blocknext block →recent activity

Analyzing

Block #74,920,290

24 transactions · 19 stateful · 2026-05-16 07:14:42 UTC

Parallelism

71/100

Blocked

58%

Avg conflicts / tx

1.63

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,920,290  ·  24 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0xac2a0273…721b

0x34b655…2a6f

14 touches
21 conflicts

0x6ee86c0c…50c6

0x34b655…2a6f

14 touches
21 conflicts

0xafd59af5…5257

0xc8689a…ee79

8 touches
6 conflicts

0x4e0ffd4d…a147

0x34b655…2a6f

8 touches
6 conflicts

0xeb0915f1…c150

0x34b655…2a6f

8 touches
6 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

8 touches
6 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

8 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: 0x34b6552d…112a6f

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity