← previous blocknext block →recent activity

Analyzing

Block #73,671,040

22 transactions · 20 stateful · 2026-05-10 12:13:02 UTC

Parallelism

86/100

Blocked

30%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,671,040  ·  22 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

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2438038…5fa7

0x34b655…2a6f

6 touches
3 conflicts

0x0520da1d…c88e

0x34b655…2a6f

4 touches
1 conflict

0x17e2d2a0…359e

0x34b655…2a6f

4 touches
1 conflict

0x218e3595…b7ca

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

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 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity