← previous blocknext block →recent activity

Analyzing

Block #73,034,242

38 transactions · 31 stateful · 2026-05-07 13:32:27 UTC

Parallelism

71/100

Blocked

58%

Avg conflicts / tx

1.71

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,034,242  ·  38 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

0xd98b3c10…67b8

0x34b655…2a6f

18 touches
36 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x47c1a8e8…f74a

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xd574ca…7ab1

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0x2f12ae8e…32a9

0xd32edf…ff58

7 touches
6 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity