← previous blocknext block →recent activity

Analyzing

Block #73,671,326

14 transactions · 13 stateful · 2026-05-10 12:14:57 UTC

Parallelism

57/100

Blocked

46%

Avg conflicts / tx

1.21

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,671,326  ·  14 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xa4e028ce…b599

0x065c9d…c394

4 touches
1 conflict

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0xd49762c9…1359

0x34b655…2a6f

4 touches
1 conflict

0xd84e22f4…ccfb

0x34b655…2a6f

4 touches
1 conflict

0xedb848fe…6534

0x34b655…2a6f

4 touches
1 conflict

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

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity