← previous blocknext block →recent activity

Analyzing

Block #72,394,645

9 transactions · 8 stateful · 2026-05-04 14:31:31 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,394,645  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xe361a3e3…4b8e

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5ff611d5…b6cd

0x065c9d…c394

4 touches
1 conflict

0x02e52757…b433

0x065c9d…c394

4 touches
1 conflict

0xa86d7e77…ca40

0x065c9d…c394

3 touches
1 conflict

0x07ee7ac4…e729

0x065c9d…c394

3 touches
1 conflict

0x375c72f6…146a

0x065c9d…c394

3 touches
1 conflict

0x49744021…34b2

0x065c9d…c394

3 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

1 conflict on slot 0xe361a3e37f…4f4b8e

← previous block·next block →recent activity