← previous blocknext block →recent activity

Analyzing

Block #74,504,854

37 transactions · 29 stateful · 2026-05-14 08:56:48 UTC

Parallelism

78/100

Blocked

45%

Avg conflicts / tx

1.03

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,504,854  ·  37 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x257251ca…49b8

0x34b655…2a6f

6 touches
3 conflicts

0xeeb38aa7…8f00

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x4e7eb462…b2ae

0x1b6862…e19c

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity