← previous blocknext block →recent activity

Analyzing

Block #73,807,058

27 transactions · 24 stateful · 2026-05-11 03:30:36 UTC

Parallelism

74/100

Blocked

58%

Avg conflicts / tx

1.44

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,807,058  ·  27 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

0x00000000…003d

0x065c9d…c394

14 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x9a555477…19a8

0x754704…b603

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x8a2657f5…e008

0x34b655…2a6f

6 touches
3 conflicts

0xb81d3ee7…3947

0x34b655…2a6f

6 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

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity