← previous blocknext block →recent activity

Analyzing

Block #73,653,858

22 transactions · 21 stateful · 2026-05-10 10:17:10 UTC

Parallelism

64/100

Blocked

67%

Avg conflicts / tx

1.5

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,653,858  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xb159af88…a9e7

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0xae69c125…2379

0x2a68ba…90c5

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x38524fae…9deb

0x34b655…2a6f

6 touches
3 conflicts

0x7f81fb82…633e

0x065c9d…c394

6 touches
3 conflicts

0xa22cdcc5…1bb0

0x065c9d…c394

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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity