← previous blocknext block →recent activity

Analyzing

Block #72,975,891

12 transactions · 11 stateful · 2026-05-07 07:04:03 UTC

Parallelism

75/100

Blocked

18%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,975,891  ·  12 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x2e1e22fd…c120

0x065c9d…c394

2 touches
0 conflicts

0x4af13f1c…577c

0x065c9d…c394

2 touches
0 conflicts

0x9c762a38…1af7

0x065c9d…c394

2 touches
0 conflicts

0xa2cc24cc…f49b

0x065c9d…c394

2 touches
0 conflicts

0xf8e2384b…f613

0x065c9d…c394

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 0xf2f76ab392…f3623e

← previous block·next block →recent activity