← previous blocknext block →recent activity

Analyzing

Block #73,223,748

32 transactions · 29 stateful · 2026-05-08 10:33:23 UTC

Parallelism

84/100

Blocked

52%

Avg conflicts / tx

0.91

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,223,748  ·  32 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xf35dca9e…bd8b

0x1b6862…e19c

8 touches
6 conflicts

0x8d0dfe2c…3345

0x2a68ba…90c5

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xfe812bf2…b428

0xd32edf…ff58

7 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

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: 0x1b68626d…2de19c

6 conflicts on slot 0x0000000000…000013

← previous block·next block →recent activity