← previous blocknext block →recent activity

Analyzing

Block #73,337,866

15 transactions · 11 stateful · 2026-05-08 23:12:30 UTC

Parallelism

73/100

Blocked

27%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,337,866  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x230de0e9…b0f4

0x065c9d…c394

2 touches
0 conflicts

0x6589f0e9…f65f

0x065c9d…c394

2 touches
0 conflicts

0x0a6f5e37…6c3c

0x34b655…2a6f

2 touches
0 conflicts

0x206f4379…e08a

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

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity