← previous blocknext block →recent activity

Analyzing

Block #73,328,507

22 transactions · 19 stateful · 2026-05-08 22:10:20 UTC

Parallelism

55/100

Blocked

58%

Avg conflicts / tx

2.32

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,328,507  ·  22 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

0x001dad39…dc6d

0xd32edf…ff58

19 touches
45 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xc2aacf41…5502

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0x46cb45de…a567

0x188d58…ea8e

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

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

45 conflicts on slot 0x001dad39ab…cadc6d

← previous block·next block →recent activity