← previous blocknext block →recent activity

Analyzing

Block #73,377,025

22 transactions · 17 stateful · 2026-05-09 03:33:00 UTC

Parallelism

73/100

Blocked

53%

Avg conflicts / tx

1.14

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,377,025  ·  22 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

0xc3c8642a…7da5

0x2a68ba…90c5

12 touches
15 conflicts

0xd3cbe661…5e1f

0x065c9d…c394

9 touches
10 conflicts

0x4d87512b…897c

0x065c9d…c394

8 touches
6 conflicts

0xf2fd77b0…5ce5

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x941ffa66…34e6

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 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 0xc3c8642ae9…317da5

← previous block·next block →recent activity