← previous blocknext block →recent activity

Analyzing

Block #74,309,348

22 transactions · 19 stateful · 2026-05-13 11:15:33 UTC

Parallelism

68/100

Blocked

58%

Avg conflicts / tx

1.27

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,309,348  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xdd172993…9dfd

0xd32edf…ff58

11 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x0f94ee4c…1898

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x46cb45de…a566

0x188d58…ea8e

6 touches
3 conflicts

0x46cb45de…a567

0x188d58…ea8e

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: 0xd32edf66…9fff58

15 conflicts on slot 0xdd17299386…6c9dfd

← previous block·next block →recent activity