← previous blocknext block →recent activity

Analyzing

Block #73,991,656

33 transactions · 30 stateful · 2026-05-12 00:01:14 UTC

Parallelism

70/100

Blocked

60%

Avg conflicts / tx

1.55

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,991,656  ·  33 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xb733232c…f4cc

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x479ce48c…fa15

0x1b6862…e19c

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

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

21 conflicts on slot 0xb733232c80…93f4cc

← previous block·next block →recent activity