← previous blocknext block →recent activity

Analyzing

Block #73,749,047

17 transactions · 14 stateful · 2026-05-10 20:59:29 UTC

Parallelism

82/100

Blocked

29%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,749,047  ·  17 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x7f81fb82…633e

0x065c9d…c394

4 touches
1 conflict

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0xe75ce681…ba60

0x188d58…ea8e

2 touches
0 conflicts

0xea02471d…1539

0x34b655…2a6f

2 touches
0 conflicts

0x12711b58…80f3

0x384275…7777

2 touches
0 conflicts

0x1167512f…b162

0x3bd359…433a

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity