← previous blocknext block →recent activity

Analyzing

Block #73,026,847

19 transactions · 16 stateful · 2026-05-07 12:43:10 UTC

Parallelism

68/100

Blocked

56%

Avg conflicts / tx

1.37

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,026,847  ·  19 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

0x0b390c61…dc07

0x065c9d…c394

10 touches
10 conflicts

0xb389d45f…8a4c

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x2f6f9356…e938

0x065c9d…c394

5 touches
3 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