← previous blocknext block →recent activity

Analyzing

Block #73,923,802

31 transactions · 26 stateful · 2026-05-11 16:28:15 UTC

Parallelism

58/100

Blocked

65%

Avg conflicts / tx

2.16

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,923,802  ·  31 txs across 13 waves  ·  depth 13
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

wave w12

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

10 touches
10 conflicts

0xee230b20…5a0f

0x34b655…2a6f

10 touches
10 conflicts

0x7e42dc9b…d20a

0xd32edf…ff58

9 touches
10 conflicts

0x7ee110ef…8394

0x34b655…2a6f

8 touches
6 conflicts

0x9d652ee8…83ca

0x34b655…2a6f

6 touches
3 conflicts

0x9d92359d…0ca7

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity