← previous blocknext block →recent activity

Analyzing

Block #74,344,811

28 transactions · 25 stateful · 2026-05-13 15:11:22 UTC

Parallelism

82/100

Blocked

64%

Avg conflicts / tx

1.21

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,344,811  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…0002

0xab3526…fa38

10 touches
10 conflicts

0xf3981be5…2c47

0x34b655…2a6f

10 touches
10 conflicts

0x00bf0542…f0c7

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0x3e04662b…0da2

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

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: 0xab35264b…1cfa38

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity