← previous blocknext block →recent activity

Analyzing

Block #74,915,074

18 transactions · 11 stateful · 2026-05-16 06:39:51 UTC

Parallelism

78/100

Blocked

27%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,915,074  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

8 touches
6 conflicts

0xea57afd0…4232

0x34b655…2a6f

6 touches
3 conflicts

0x97b0b2ee…4666

0x34b655…2a6f

5 touches
3 conflicts

0x388f889f…a655

0x34b655…2a6f

5 touches
3 conflicts

0xdd2c59b1…780f

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

6 conflicts on slot 0xf3d10975b0…050d07

← previous block·next block →recent activity