← previous blocknext block →recent activity

Analyzing

Block #72,974,793

22 transactions · 17 stateful · 2026-05-07 06:56:43 UTC

Parallelism

64/100

Blocked

53%

Avg conflicts / tx

0.82

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,974,793  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x70b2f813…783c

0x2a68ba…90c5

8 touches
6 conflicts

0x6832669b…099c

0xd32edf…ff58

7 touches
6 conflicts

0x395d6cbf…f420

0x065c9d…c394

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c5

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x70b2f81398…04783c

← previous block·next block →recent activity