← previous blocknext block →recent activity

Analyzing

Block #74,309,412

21 transactions · 20 stateful · 2026-05-13 11:15:58 UTC

Parallelism

52/100

Blocked

65%

Avg conflicts / tx

2.24

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,309,412  ·  21 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xa91c899f…6ee3

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xee2bb5dd…99f2

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xe937b6bc…8a55

0x1b6862…e19c

6 touches
3 conflicts

0x1c840894…764a

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity