Block #73,918,573

← previous blocknext block →recent activity

Analyzing

Block #73,918,573

11 transactions · 9 stateful · 2026-05-11 15:53:27 UTC

Parallelism

64/100

Blocked

33%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,918,573  ·  11 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

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x36e7160a…969d

0x065c9d…c394

3 touches
1 conflict

0xd643b79d…fc74

0x065c9d…c394

3 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x1a7b2836…f522

0x58e158…3d57

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