← previous blocknext block →recent activity

Analyzing

Block #73,476,245

8 transactions · 7 stateful · 2026-05-09 14:33:16 UTC

Parallelism

50/100

Blocked

43%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,476,245  ·  8 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0xc7a29bab…e3b8

0x065c9d…c394

4 touches
1 conflict

0x45c8ce08…0271

0x065c9d…c394

4 touches
1 conflict

0xfef8599a…7ba7

0x065c9d…c394

3 touches
1 conflict

0x11b8b154…a119

0x065c9d…c394

3 touches
1 conflict

0x66de0ce3…337a

0x188d58…ea8e

2 touches
0 conflicts

0x66de0ce3…337c

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

← previous block·next block →recent activity