← previous blocknext block →recent activity

Analyzing

Block #73,328,465

31 transactions · 21 stateful · 2026-05-08 22:10:04 UTC

Parallelism

61/100

Blocked

57%

Avg conflicts / tx

2.39

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,328,465  ·  31 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xc8714fc5…c0e9

0xd32edf…ff58

23 touches
66 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x91ecc547…33f0

0x1b6862…e19c

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x46cb45de…a566

0x188d58…ea8e

6 touches
3 conflicts

0x46cb45de…a567

0x188d58…ea8e

6 touches
3 conflicts

0x846f2172…fd54

0x0555e3…2b9c

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

66 conflicts on slot 0xc8714fc5b7…1ac0e9

← previous block·next block →recent activity