← previous blocknext block →recent activity

Analyzing

Block #73,035,397

30 transactions · 25 stateful · 2026-05-07 13:40:07 UTC

Parallelism

70/100

Blocked

68%

Avg conflicts / tx

1.4

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,035,397  ·  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

0x00000000…0002

0xd574ca…7ab1

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xdaca243a…f9de

0x34b655…2a6f

6 touches
3 conflicts

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 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: 0xd574cae5…037ab1

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity