← previous blocknext block →recent activity

Analyzing

Block #73,749,125

33 transactions · 24 stateful · 2026-05-10 21:00:01 UTC

Parallelism

82/100

Blocked

58%

Avg conflicts / tx

1.09

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,749,125  ·  33 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x15d039e7…4bb6

0x34b655…2a6f

8 touches
6 conflicts

0x7f81fb82…633e

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

6 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

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

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity