← previous blocknext block →recent activity

Analyzing

Block #73,654,882

10 transactions · 9 stateful · 2026-05-10 10:24:05 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,654,882  ·  10 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x51087f5a…61f7

0x34b655…2a6f

2 touches
0 conflicts

0x37e1be01…6f19

0x54cd53…9e7d

2 touches
0 conflicts

0xa27fa22d…7dca

0x54cd53…9e7d

2 touches
0 conflicts

0x0b3b753c…589a

0x6657d1…8ccc

2 touches
0 conflicts

0x0d28bad1…ec25

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity