← previous blocknext block →recent activity

Analyzing

Block #73,050,781

32 transactions · 18 stateful · 2026-05-07 15:22:36 UTC

Parallelism

81/100

Blocked

50%

Avg conflicts / tx

0.38

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,050,781  ·  32 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

0x8e66da19…66b6

0x065c9d…c394

6 touches
3 conflicts

0x2371df3d…9b63

0xd32edf…ff58

5 touches
3 conflicts

0x5e8560d4…d380

0x065c9d…c394

4 touches
1 conflict

0x6c9159fe…1b1c

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

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

3 conflicts on slot 0x8e66da1932…c966b6

← previous block·next block →recent activity