← previous blocknext block →recent activity

Analyzing

Block #73,396,860

25 transactions · 14 stateful · 2026-05-09 05:45:00 UTC

Parallelism

84/100

Blocked

29%

Avg conflicts / tx

0.28

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,396,860  ·  25 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

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x26469d28…5013

0xd32edf…ff58

3 touches
1 conflict

0x33018431…8f5c

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5d

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity