← previous blocknext block →recent activity

Analyzing

Block #74,332,584

34 transactions · 25 stateful · 2026-05-13 13:50:04 UTC

Parallelism

82/100

Blocked

52%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,332,584  ·  34 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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x8a35acfb…d1a7

0x8d66a4…3095

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0xe3aab3ec…a6dd

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0x5a3732cb…edad

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x0711ec2d…d973

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity