← previous blocknext block →recent activity

Analyzing

Block #74,589,934

30 transactions · 24 stateful · 2026-05-14 18:29:28 UTC

Parallelism

67/100

Blocked

54%

Avg conflicts / tx

1.5

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,589,934  ·  30 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

0xd98b3c10…67b8

0x34b655…2a6f

18 touches
36 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xff57dec4…6482

0x34b655…2a6f

6 touches
3 conflicts

0x84aef2aa…979f

0x34b655…2a6f

6 touches
3 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity