← previous blocknext block →recent activity

Analyzing

Block #73,338,538

29 transactions · 17 stateful · 2026-05-08 23:16:58 UTC

Parallelism

69/100

Blocked

65%

Avg conflicts / tx

1.59

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,338,538  ·  29 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

0x8f51e3b7…a304

0xd32edf…ff58

17 touches
36 conflicts

0x46cb45de…a567

0x188d58…ea8e

10 touches
10 conflicts

0x46cb45de…a566

0x188d58…ea8e

10 touches
10 conflicts

0x09beabbc…065c

0x188d58…ea8e

6 touches
3 conflicts

0x09beabbc…065d

0x188d58…ea8e

6 touches
3 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

4 touches
1 conflict

0xf26eda05…0203

0xd18b7e…414b

4 touches
1 conflict

0x1c354dc0…96de

0x754704…b603

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

36 conflicts on slot 0x8f51e3b767…8fa304

← previous block·next block →recent activity