← previous blocknext block →recent activity

Analyzing

Block #73,493,021

9 transactions · 9 stateful · 2026-05-09 16:24:57 UTC

Parallelism

56/100

Blocked

33%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,493,021  ·  9 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xa27fa22d…7dca

0x54cd53…9e7d

2 touches
0 conflicts

0x02952e27…66f1

0x6657d1…8ccc

2 touches
0 conflicts

0x1300688c…0a60

0x6657d1…8ccc

2 touches
0 conflicts

0x3fed68a4…90ac

0x6657d1…8ccc

2 touches
0 conflicts

0x4a542d80…697d

0x6657d1…8ccc

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity