← previous blocknext block →recent activity

Analyzing

Block #73,676,419

12 transactions · 9 stateful · 2026-05-10 12:49:27 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,676,419  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0x24f9d51b…d26c

0x065c9d…c394

2 touches
0 conflicts

0x2c0a8b66…2ffd

0x065c9d…c394

2 touches
0 conflicts

0x4887f4ab…414b

0x065c9d…c394

2 touches
0 conflicts

0xa3423131…7369

0x065c9d…c394

2 touches
0 conflicts

0xe3012deb…de6d

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity