← previous blocknext block →recent activity

Analyzing

Block #73,200,926

9 transactions · 8 stateful · 2026-05-08 08:01:32 UTC

Parallelism

56/100

Blocked

38%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,200,926  ·  9 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

6 touches
3 conflicts

0xdfaff12f…b4d0

0x065c9d…c394

6 touches
3 conflicts

0x2a354a63…0515

0x065c9d…c394

6 touches
3 conflicts

0x8e66da19…66b6

0x065c9d…c394

6 touches
3 conflicts

0xa152a791…ec2f

0x065c9d…c394

5 touches
3 conflicts

0x4e5ebbf7…ae70

0xc8689a…ee79

4 touches
1 conflict

0x7f189cf6…afab

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity