← previous blocknext block →recent activity

Analyzing

Block #74,420,898

31 transactions · 27 stateful · 2026-05-13 23:37:41 UTC

Parallelism

71/100

Blocked

59%

Avg conflicts / tx

1.06

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,420,898  ·  31 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x0c8d2080…b71a

0xd32edf…ff58

9 touches
10 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

6 touches
3 conflicts

0xd025d7d7…f05a

0x3bd359…433a

6 touches
3 conflicts

0x5a3732cb…edaf

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x00000000…0013

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: 0x754704bc…afb603

10 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity