← previous blocknext block →recent activity

Analyzing

Block #73,046,180

37 transactions · 32 stateful · 2026-05-07 14:51:54 UTC

Parallelism

70/100

Blocked

66%

Avg conflicts / tx

1.65

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,046,180  ·  37 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x17064d39…9a8a

0xd32edf…ff58

15 touches
28 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x70b2f813…783c

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002f

0x1b6862…e19c

6 touches
3 conflicts

0xc2aacf41…5504

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

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: 0xd32edf66…9fff58

28 conflicts on slot 0x17064d3981…529a8a

← previous block·next block →recent activity