← previous blocknext block →recent activity

Analyzing

Block #73,795,902

23 transactions · 22 stateful · 2026-05-11 02:15:38 UTC

Parallelism

74/100

Blocked

45%

Avg conflicts / tx

1.22

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,795,902  ·  23 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

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x7b50a82b…f53d

0x34b655…2a6f

10 touches
10 conflicts

0xb378025c…30cf

0x34b655…2a6f

10 touches
10 conflicts

0xd49762c9…1359

0x34b655…2a6f

10 touches
10 conflicts

0xdf7899c0…c53a

0x34b655…2a6f

10 touches
10 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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity