← previous blocknext block →recent activity

Analyzing

Block #73,212,051

38 transactions · 26 stateful · 2026-05-08 09:15:27 UTC

Parallelism

79/100

Blocked

50%

Avg conflicts / tx

0.82

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,212,051  ·  38 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xc1a2660a…76a4

0xd32edf…ff58

9 touches
10 conflicts

0x27b7121f…bc30

0x34b655…2a6f

8 touches
6 conflicts

0x7f189cf6…afab

0x065c9d…c394

8 touches
6 conflicts

0xf4730a2d…3538

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

6 touches
3 conflicts

0xac206e47…ef7d

0x34b655…2a6f

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

10 conflicts on slot 0xc1a2660a7f…8776a4

← previous block·next block →recent activity