← previous blocknext block →recent activity

Analyzing

Block #73,744,736

37 transactions · 25 stateful · 2026-05-10 20:30:22 UTC

Parallelism

76/100

Blocked

52%

Avg conflicts / tx

1.16

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,744,736  ·  37 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

0xe30b1c7e…3de8

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xae69c125…2379

0x2a68ba…90c5

4 touches
2 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x018e78e3…4560

0x065c9d…c394

3 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: 0xd32edf66…9fff58

36 conflicts on slot 0xe30b1c7e5c…3f3de8

← previous block·next block →recent activity