← previous blocknext block →recent activity

Analyzing

Block #73,042,147

25 transactions · 22 stateful · 2026-05-07 14:25:01 UTC

Parallelism

72/100

Blocked

55%

Avg conflicts / tx

1.36

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,042,147  ·  25 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

0x388e001a…7e04

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x61ad45b1…15ac

0x34b655…2a6f

10 touches
10 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

8 touches
6 conflicts

0x908d4442…2c4b

0x34b655…2a6f

8 touches
6 conflicts

0x8a85cf3d…2868

0x34b655…2a6f

8 touches
6 conflicts

0x4a03ceb5…a07f

0x34b655…2a6f

8 touches
6 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: 0x34b6552d…112a6f

15 conflicts on slot 0x388e001a16…e57e04

← previous block·next block →recent activity