← previous blocknext block →recent activity

Analyzing

Block #73,921,085

38 transactions · 30 stateful · 2026-05-11 16:10:10 UTC

Parallelism

68/100

Blocked

70%

Avg conflicts / tx

1.84

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,921,085  ·  38 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x4bd581b2…0afb

0xd32edf…ff58

13 touches
21 conflicts

0x578e7f66…1b56

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x9be2b99a…a959

0x34b655…2a6f

10 touches
10 conflicts

0xac8e97a0…8426

0x34b655…2a6f

10 touches
10 conflicts

0xbc3d6b37…2215

0x34b655…2a6f

10 touches
10 conflicts

0x4f483049…3cc7

0x34b655…2a6f

10 touches
10 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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity