← previous blocknext block →recent activity

Analyzing

Block #73,673,595

14 transactions · 14 stateful · 2026-05-10 12:30:20 UTC

Parallelism

64/100

Blocked

36%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,673,595  ·  14 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

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x529acb6a…fcc6

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x2ed6e329…5e08

0x0c65a0…0852

2 touches
0 conflicts

0x5cbda340…37bb

0x0c65a0…0852

2 touches
0 conflicts

0x5db918ef…f1ef

0x0c65a0…0852

2 touches
0 conflicts

0xa5e083bb…11e7

0x0c65a0…0852

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

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity