← previous blocknext block →recent activity

Analyzing

Block #73,372,579

15 transactions · 13 stateful · 2026-05-09 03:03:26 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,372,579  ·  15 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

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

3 conflicts on slot 0x6f08361da9…89bda6

← previous block·next block →recent activity