← previous blocknext block →recent activity

Analyzing

Block #73,328,207

16 transactions · 13 stateful · 2026-05-08 22:08:23 UTC

Parallelism

75/100

Blocked

23%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,328,207  ·  16 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

0x56a919c4…ab49

0xee8c0e…1242

8 touches
6 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

6 touches
3 conflicts

0x00f7e3b7…e017

0x188d58…ea8e

6 touches
3 conflicts

0x05b8b0b5…5b6c

0x065c9d…c394

2 touches
0 conflicts

0xf537eaa0…73c8

0x065c9d…c394

2 touches
0 conflicts

0x729c91b8…9537

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9539

0x188d58…ea8e

2 touches
0 conflicts

0xbdff944d…447e

0x2a68ba…90c5

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: 0xee8c0e9f…481242

6 conflicts on slot 0x56a919c43e…27ab49

← previous block·next block →recent activity