← previous blocknext block →recent activity

Analyzing

Block #73,043,128

35 transactions · 18 stateful · 2026-05-07 14:31:34 UTC

Parallelism

86/100

Blocked

28%

Avg conflicts / tx

0.31

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,043,128  ·  35 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

0xc52a05ec…23b8

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb87

0x1b6862…e19c

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

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

10 conflicts on slot 0xc52a05ec26…dc23b8

← previous block·next block →recent activity