← previous blocknext block →recent activity

Analyzing

Block #74,407,016

23 transactions · 19 stateful · 2026-05-13 22:05:23 UTC

Parallelism

65/100

Blocked

58%

Avg conflicts / tx

1.43

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,407,016  ·  23 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

14 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x8902ba1f…f4b6

0x34b655…2a6f

8 touches
6 conflicts

0xea2d3331…6e34

0x1b6862…e19c

6 touches
3 conflicts

0x9b8800c1…ed12

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

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: 0x34b6552d…112a6f

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity