← previous blocknext block →recent activity

Analyzing

Block #73,975,250

22 transactions · 14 stateful · 2026-05-11 22:10:49 UTC

Parallelism

82/100

Blocked

21%

Avg conflicts / tx

0.27

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,975,250  ·  22 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

0xe6455d1f…1029

0x754704…b603

8 touches
6 conflicts

0x0d0b2509…074d

0x3bd359…433a

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xd0f7d137…fb21

0x065c9d…c394

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00f7e3b7…e016

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9537

0x188d58…ea8e

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

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: 0x754704bc…afb603

6 conflicts on slot 0xe6455d1fbe…eb1029

← previous block·next block →recent activity