← previous blocknext block →recent activity

Analyzing

Block #72,984,183

24 transactions · 16 stateful · 2026-05-07 07:59:30 UTC

Parallelism

75/100

Blocked

31%

Avg conflicts / tx

0.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,984,183  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xe8013b93…bf3a

0xd32edf…ff58

9 touches
10 conflicts

0xd996735f…8734

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002e

0x1b6862…e19c

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: 0xd32edf66…9fff58

10 conflicts on slot 0xe8013b9337…b5bf3a

← previous block·next block →recent activity