← previous blocknext block →recent activity

Analyzing

Block #73,651,920

12 transactions · 12 stateful · 2026-05-10 10:04:04 UTC

Parallelism

75/100

Blocked

25%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,651,920  ·  12 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0xf9023f16…3edf

0xd32edf…ff58

3 touches
1 conflict

0x06b1b742…3b12

0x065c9d…c394

2 touches
0 conflicts

0x4fdd18bf…74a7

0x065c9d…c394

2 touches
0 conflicts

0x54d58aea…e15c

0x065c9d…c394

2 touches
0 conflicts

0x310a7246…2dcb

0x34b655…2a6f

2 touches
0 conflicts

0xfe39a1f7…8eb0

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity