← previous blocknext block →recent activity

Analyzing

Block #73,869,285

12 transactions · 9 stateful · 2026-05-11 10:25:05 UTC

Parallelism

67/100

Blocked

44%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,869,285  ·  12 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

0x00000000…0007

0x1414f3…5137

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6778fbb0…f3cb

0x065c9d…c394

2 touches
0 conflicts

0x7f81fb82…633e

0x065c9d…c394

2 touches
0 conflicts

0xd0d070e3…67e4

0x065c9d…c394

2 touches
0 conflicts

0x0802cba3…292c

0x1414f3…5137

2 touches
0 conflicts

0x1fe5e332…4e47

0x1414f3…5137

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: 0x1414f3ba…045137

6 conflicts on slot 0x0000000000…000007

← previous block·next block →recent activity