← previous blocknext block →recent activity

Analyzing

Block #73,391,202

30 transactions · 22 stateful · 2026-05-09 05:07:17 UTC

Parallelism

70/100

Blocked

55%

Avg conflicts / tx

1.43

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,391,202  ·  30 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

0x22e295f5…1bef

0x065c9d…c394

12 touches
15 conflicts

0xe038916c…b1be

0x2a68ba…90c5

12 touches
15 conflicts

0x54ff6cf9…e486

0xd32edf…ff58

11 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb86

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

8 touches
6 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 0x22e295f5d8…ac1bef

← previous block·next block →recent activity