← previous blocknext block →recent activity

Analyzing

Block #73,987,413

11 transactions · 9 stateful · 2026-05-11 23:32:32 UTC

Parallelism

55/100

Blocked

67%

Avg conflicts / tx

1.09

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,987,413  ·  11 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x44f01bef…0d17

0x065c9d…c394

4 touches
1 conflict

0xfcd17a98…e3ce

0x065c9d…c394

4 touches
1 conflict

0xa2c1f030…0f44

0x065c9d…c394

3 touches
1 conflict

0x4b0c1709…f166

0x065c9d…c394

3 touches
1 conflict

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