← previous blocknext block →recent activity

Analyzing

Block #73,261,428

14 transactions · 11 stateful · 2026-05-08 14:43:51 UTC

Parallelism

79/100

Blocked

18%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,261,428  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0a2250a8…3cb1

0x34b655…2a6f

2 touches
0 conflicts

0x0f41c833…9c38

0x34b655…2a6f

2 touches
0 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

2 touches
0 conflicts

0x2d5e75ab…5b6d

0x34b655…2a6f

2 touches
0 conflicts

0x388e001a…7e04

0x34b655…2a6f

2 touches
0 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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity