← previous blocknext block →recent activity

Analyzing

Block #73,798,645

17 transactions · 15 stateful · 2026-05-11 02:34:07 UTC

Parallelism

59/100

Blocked

40%

Avg conflicts / tx

1.24

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,798,645  ·  17 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x7f81fb82…633e

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x6f2e60dc…e661

0x34b655…2a6f

2 touches
0 conflicts

0x736c5b69…fb3f

0x34b655…2a6f

2 touches
0 conflicts

0xa37c1031…c3f0

0x34b655…2a6f

2 touches
0 conflicts

0xac2a0273…721b

0x34b655…2a6f

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

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity