← previous blocknext block →recent activity

Analyzing

Block #73,273,854

14 transactions · 12 stateful · 2026-05-08 16:06:37 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,273,854  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x8e80434a…a96d

0x0555e3…2b9c

2 touches
0 conflicts

0x684443d5…c0fc

0x065c9d…c394

2 touches
0 conflicts

0xb72a632d…cf10

0x065c9d…c394

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity