← previous blocknext block →recent activity

Analyzing

Block #73,961,328

16 transactions · 14 stateful · 2026-05-11 20:37:48 UTC

Parallelism

75/100

Blocked

43%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,961,328  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xee230b20…5a0f

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x7b1b74a7…9206

0x3bd359…433a

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x41be85…e2bd

6 touches
3 conflicts

0x00000000…0001

0x41be85…e2bd

6 touches
3 conflicts

0x072430d8…35ad

0xed8924…7777

6 touches
3 conflicts

0xd98b3c10…67b8

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

6 conflicts on slot 0xee230b202a…c05a0f

← previous block·next block →recent activity