← previous blocknext block →recent activity

Analyzing

Block #73,683,230

28 transactions · 25 stateful · 2026-05-10 13:35:28 UTC

Parallelism

61/100

Blocked

52%

Avg conflicts / tx

1.71

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,683,230  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x0ac31945…2c72

0x065c9d…c394

14 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

14 touches
21 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x529acb6a…fcc6

0x065c9d…c394

8 touches
6 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

6 touches
3 conflicts

0xe96c91d2…32ff

0x8d66a4…3095

4 touches
1 conflict

0x7f430e47…4cbd

0x8d66a4…3095

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

21 conflicts on slot 0x0ac3194537…8f2c72

← previous block·next block →recent activity