← previous blocknext block →recent activity

Analyzing

Block #74,344,883

44 transactions · 35 stateful · 2026-05-13 15:11:51 UTC

Parallelism

75/100

Blocked

60%

Avg conflicts / tx

1.52

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,344,883  ·  44 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x77c03270…cac9

0xd32edf…ff58

17 touches
36 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0xe783dfa4…5494

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x57b024e8…0042

0x065c9d…c394

8 touches
6 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 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

36 conflicts on slot 0x77c0327003…a2cac9

← previous block·next block →recent activity