← previous blocknext block →recent activity

Analyzing

Block #73,383,939

17 transactions · 15 stateful · 2026-05-09 04:18:58 UTC

Parallelism

41/100

Blocked

60%

Avg conflicts / tx

1.88

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,383,939  ·  17 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

14 touches
21 conflicts

0xb159af88…a9e7

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x37179e06…0f0a

0x065c9d…c394

2 touches
0 conflicts

0x749d2d67…f222

0x065c9d…c394

2 touches
0 conflicts

0x7f81fb82…633e

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

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity