← previous blocknext block →recent activity

Analyzing

Block #73,651,917

36 transactions · 24 stateful · 2026-05-10 10:04:02 UTC

Parallelism

81/100

Blocked

54%

Avg conflicts / tx

0.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,651,917  ·  36 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

0x246cdede…2e00

0xd32edf…ff58

11 touches
15 conflicts

0x846f2172…fd54

0x0555e3…2b9c

8 touches
6 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0x46cb45de…a567

0x188d58…ea8e

6 touches
3 conflicts

0xac206e47…ef7d

0x34b655…2a6f

6 touches
3 conflicts

0xbc8997d6…2e0b

0x34b655…2a6f

6 touches
3 conflicts

0xf2438038…5fa7

0x34b655…2a6f

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

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: 0xd32edf66…9fff58

15 conflicts on slot 0x246cdedec1…902e00

← previous block·next block →recent activity