← previous blocknext block →recent activity

Analyzing

Block #74,346,754

27 transactions · 21 stateful · 2026-05-13 15:24:20 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.44

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,346,754  ·  27 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xc16e646d…4fb0

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0x44d7acbf…e67b

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x0711ec2d…d973

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity