← previous blocknext block →recent activity

Analyzing

Block #73,372,861

17 transactions · 17 stateful · 2026-05-09 03:05:19 UTC

Parallelism

53/100

Blocked

53%

Avg conflicts / tx

1.82

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,372,861  ·  17 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

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x41521e95…0475

0x065c9d…c394

2 touches
0 conflicts

0x6e87c2cb…15af

0x065c9d…c394

2 touches
0 conflicts

0x801ce376…d74c

0x065c9d…c394

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

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity