← previous blocknext block →recent activity

Analyzing

Block #73,043,109

36 transactions · 27 stateful · 2026-05-07 14:31:27 UTC

Parallelism

83/100

Blocked

48%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,043,109  ·  36 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

0xf01df3a7…9e5c

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0x3b8ffd61…f3ad

0x34b655…2a6f

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

6 touches
3 conflicts

0x7f189cf6…afab

0x065c9d…c394

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

15 conflicts on slot 0xf01df3a710…e89e5c

← previous block·next block →recent activity