← previous blocknext block →recent activity

Analyzing

Block #74,456,941

41 transactions · 25 stateful · 2026-05-14 03:37:45 UTC

Parallelism

78/100

Blocked

60%

Avg conflicts / tx

0.85

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,456,941  ·  41 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

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x5cfec795…7c0e

0x34b655…2a6f

8 touches
6 conflicts

0x874cb67f…26de

0x1b6862…e19c

6 touches
3 conflicts

0x01737532…9b12

0x34b655…2a6f

6 touches
3 conflicts

0x2acc1b4e…92a5

0x34b655…2a6f

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 0xac2a02739b…81721b

← previous block·next block →recent activity