← previous blocknext block →recent activity

Analyzing

Block #73,328,210

32 transactions · 23 stateful · 2026-05-08 22:08:24 UTC

Parallelism

84/100

Blocked

48%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,328,210  ·  32 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xec390a27…6110

0xd32edf…ff58

9 touches
10 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x46cb45de…a566

0x188d58…ea8e

6 touches
3 conflicts

0x46cb45de…a568

0x188d58…ea8e

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x846f2172…fd54

0x0555e3…2b9c

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x5d82c9b5…004c

0x3bd359…433a

4 touches
1 conflict

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

10 conflicts on slot 0xec390a27b2…c06110

← previous block·next block →recent activity