← previous blocknext block →recent activity

Analyzing

Block #73,337,797

19 transactions · 18 stateful · 2026-05-08 23:12:03 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,337,797  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x0b390c61…dc07

0x065c9d…c394

10 touches
10 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x6ffceff8…3283

0xd32edf…ff58

3 touches
1 conflict

0x89f3104d…b3fe

0x065c9d…c394

3 touches
1 conflict

0x86b12065…1319

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity