← previous blocknext block →recent activity

Analyzing

Block #73,396,885

13 transactions · 12 stateful · 2026-05-09 05:45:10 UTC

Parallelism

54/100

Blocked

50%

Avg conflicts / tx

1.08

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,396,885  ·  13 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0xe038916c…b1be

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xcd8e11b4…a578

0x065c9d…c394

5 touches
3 conflicts

0x94cfb3ea…ceb7

0x065c9d…c394

4 touches
1 conflict

0xf8480e2a…dff4

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 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

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity