← previous blocknext block →recent activity

Analyzing

Block #73,214,556

25 transactions · 18 stateful · 2026-05-08 09:32:06 UTC

Parallelism

72/100

Blocked

39%

Avg conflicts / tx

0.64

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,214,556  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

8 touches
6 conflicts

0xb2ab97de…9713

0xd32edf…ff58

7 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x97a0cd85…cfca

0x080ec9…fe74

4 touches
1 conflict

0x56a919c4…ab49

0xe7cd86…c82d

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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: 0x188d586d…f9ea8e

6 conflicts on slot 0x01e7b86585…4d6e6d

← previous block·next block →recent activity