← previous blocknext block →recent activity

Analyzing

Block #73,223,750

24 transactions · 18 stateful · 2026-05-08 10:33:23 UTC

Parallelism

58/100

Blocked

67%

Avg conflicts / tx

2.21

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,223,750  ·  24 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x488dcc24…9dd7

0xd32edf…ff58

19 touches
45 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

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

45 conflicts on slot 0x488dcc24f5…fa9dd7

← previous block·next block →recent activity