← previous blocknext block →recent activity

Analyzing

Block #73,201,928

31 transactions · 22 stateful · 2026-05-08 08:08:12 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.94

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,201,928  ·  31 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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…003d

0x065c9d…c394

14 touches
21 conflicts

0x7f189cf6…afab

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

4 touches
1 conflict

0xe53ee0ec…6128

0xd32edf…ff58

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: 0x065c9d28…a9c394

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity