← previous blocknext block →recent activity

Analyzing

Block #73,372,886

34 transactions · 24 stateful · 2026-05-09 03:05:29 UTC

Parallelism

59/100

Blocked

67%

Avg conflicts / tx

2.85

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #73,372,886  ·  34 txs across 14 waves  ·  depth 14
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

wave w12

wave w13

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

0x72b7ec63…20f6

0xd32edf…ff58

27 touches
91 conflicts

0x4d87512b…897c

0x065c9d…c394

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002e

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

91 conflicts on slot 0x72b7ec63de…3720f6

← previous block·next block →recent activity