← previous blocknext block →recent activity

Analyzing

Block #73,034,218

37 transactions · 31 stateful · 2026-05-07 13:32:17 UTC

Parallelism

78/100

Blocked

61%

Avg conflicts / tx

1.51

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,034,218  ·  37 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x388e001a…7e04

0x34b655…2a6f

10 touches
10 conflicts

0xe7574014…95e2

0x34b655…2a6f

8 touches
6 conflicts

0x5dc14a96…6816

0x34b655…2a6f

8 touches
6 conflicts

0x375b6201…9c1e

0x34b655…2a6f

8 touches
6 conflicts

0x08743888…4694

0xd32edf…ff58

7 touches
6 conflicts

0xaef9058e…322a

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity