← previous blocknext block →recent activity

Analyzing

Block #74,595,739

35 transactions · 26 stateful · 2026-05-14 19:08:18 UTC

Parallelism

71/100

Blocked

69%

Avg conflicts / tx

1.37

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,595,739  ·  35 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

12 touches
15 conflicts

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1a6

0x8d66a4…3095

8 touches
6 conflicts

0x703307bc…8fcf

0x34b655…2a6f

6 touches
3 conflicts

0x0335ae80…8414

0x8d66a4…3095

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity