← previous blocknext block →recent activity

Analyzing

Block #72,984,191

15 transactions · 10 stateful · 2026-05-07 07:59:33 UTC

Parallelism

73/100

Blocked

30%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,984,191  ·  15 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

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0xf91a2adb…d29e

0x065c9d…c394

3 touches
1 conflict

0x7f27f809…1c5a

0x065c9d…c394

3 touches
1 conflict

0xde1fa2a6…d286

0x065c9d…c394

3 touches
1 conflict

0x151af2a0…b509

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity