← previous blocknext block →recent activity

Analyzing

Block #74,765,283

32 transactions · 26 stateful · 2026-05-15 14:00:24 UTC

Parallelism

88/100

Blocked

54%

Avg conflicts / tx

0.66

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,765,283  ·  32 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x07ab51b8…0f13

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x7bec953c…dd6f

0xd32edf…ff58

5 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

5 touches
3 conflicts

0x00000000…001a

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: 0x34b6552d…112a6f

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity