← previous blocknext block →recent activity

Analyzing

Block #73,043,193

35 transactions · 32 stateful · 2026-05-07 14:32:01 UTC

Parallelism

74/100

Blocked

59%

Avg conflicts / tx

1.71

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,043,193  ·  35 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x554da6d0…6241

0xd32edf…ff58

13 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

10 touches
10 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

21 conflicts on slot 0x554da6d082…4e6241

← previous block·next block →recent activity