← previous blocknext block →recent activity

Analyzing

Block #74,631,659

32 transactions · 28 stateful · 2026-05-14 23:08:25 UTC

Parallelism

75/100

Blocked

46%

Avg conflicts / tx

0.94

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,631,659  ·  32 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x7a106952…e864

0xd32edf…ff58

13 touches
21 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x1686502b…a1d2

0x3bd359…433a

4 touches
1 conflict

0x5d82c9b5…004c

0x3bd359…433a

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0xdd70bea3…1ffe

0x3bd359…433a

4 touches
1 conflict

0x00000000…0003

0x5afd3e…7620

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

21 conflicts on slot 0x7a106952fc…c0e864

← previous block·next block →recent activity