← previous blocknext block →recent activity

Analyzing

Block #74,463,513

43 transactions · 29 stateful · 2026-05-14 04:21:30 UTC

Parallelism

81/100

Blocked

55%

Avg conflicts / tx

0.98

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,463,513  ·  43 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

0x8a531ecd…58db

0xd32edf…ff58

15 touches
28 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x85a88798…f85e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

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: 0xd32edf66…9fff58

28 conflicts on slot 0x8a531ecd1c…1e58db

← previous block·next block →recent activity