← previous blocknext block →recent activity

Analyzing

Block #73,502,332

13 transactions · 12 stateful · 2026-05-09 17:26:56 UTC

Parallelism

31/100

Blocked

67%

Avg conflicts / tx

2.08

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,502,332  ·  13 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0x4d87512b…897c

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x488cba5c…9655

0x065c9d…c394

3 touches
1 conflict

0x9cd25f5e…44db

0x065c9d…c394

3 touches
1 conflict

0xcb45d9d6…cb80

0x1b6862…e19c

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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity