← previous blocknext block →recent activity

Analyzing

Block #73,748,987

13 transactions · 11 stateful · 2026-05-10 20:59:05 UTC

Parallelism

69/100

Blocked

36%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,748,987  ·  13 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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0xe0186c7f…ec47

0x065c9d…c394

4 touches
1 conflict

0x9ff1dcc6…9d1f

0x065c9d…c394

2 touches
0 conflicts

0xe5f75f37…afb6

0x065c9d…c394

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

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

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity