← previous blocknext block →recent activity

Analyzing

Block #74,413,467

35 transactions · 28 stateful · 2026-05-13 22:48:20 UTC

Parallelism

83/100

Blocked

61%

Avg conflicts / tx

0.97

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,413,467  ·  35 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x1c389468…6b0e

0x34b655…2a6f

10 touches
10 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x0cffa3d2…ef10

0xd32edf…ff58

7 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

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

10 conflicts on slot 0x1c38946843…a16b0e

← previous block·next block →recent activity