← previous blocknext block →recent activity

Analyzing

Block #73,308,293

23 transactions · 15 stateful · 2026-05-08 19:55:45 UTC

Parallelism

74/100

Blocked

33%

Avg conflicts / tx

0.48

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,308,293  ·  23 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

0xf50ebb3a…863e

0xd32edf…ff58

9 touches
10 conflicts

0xfa50e6d5…196b

0x065c9d…c394

3 touches
1 conflict

0xd938d129…e95c

0x065c9d…c394

3 touches
1 conflict

0xa88828a7…2d7f

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 conflicts

0x8d0dfe2c…3345

0x2a68ba…90c5

2 touches
0 conflicts

0x51087f5a…61f7

0x34b655…2a6f

2 touches
0 conflicts

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

10 conflicts on slot 0xf50ebb3a71…9e863e

← previous block·next block →recent activity