← previous blocknext block →recent activity

Analyzing

Block #74,338,624

26 transactions · 19 stateful · 2026-05-13 14:30:16 UTC

Parallelism

69/100

Blocked

63%

Avg conflicts / tx

1.04

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,338,624  ·  26 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xb7bacea4…223c

0xd32edf…ff58

11 touches
15 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0xd53220ed…4735

0x1b6862…e19c

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0019

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

15 conflicts on slot 0xb7bacea492…a6223c

← previous block·next block →recent activity